mastodon - Link to source

Tiny new feature: Checkboxes in a message.

No, I'm not gonna make it a full blown task list app 😜 but it happens quite often, that my wife sends me a list of groceries when I'm walking to the supermarket. This way I'm now able to check, what I have already in my cart so I don't forget anything.

It works by sending special reactions under the hood. So anyone with reaction sending permissions in a room can check any box from any sender.

What do you think?

#matrix #fluffychat @matrix

#matrix #fluffychat @The Matrix.org Foundation
in reply to chebra

gotosocial - Link to source

Shine

WhatsApp and other closed source apps have a full dictatorship over the whole protocol and all clients. They can experiment with new features on all users at once, and they can turn them off if they don't meet the expectations for all at once.

How exactly do you want to do this in open world? Some clients will inevitably lag behind, some clients will not implement all features. Even if you didn't allow other clients to experiment with API proposals, they would lag behind the upstream.

The only thing you can do is to give developers tools to create reasonable fallback.

in reply to Shine

mastodon - Link to source

chebra

@shine It's not that hard. You just have to open your mind. Instead of invisible reactions this could be sending normal text messages `*Adam checked [x] option one` and supporting clients would render it as a checked checkbox, but unsupporting clients would at least have a meaningful fallback. The problem here is that Krille totally forgot to think about the unsupporting clients. And that's how we lose people.
@Shine
⇧