5 ms·

The Terrible UX is in part from the protocol, clients can't fix that (just look at the absolute mess that rooms are). And still no support for custom emoji or s

by zaarn 5y ago

The Terrible UX is in part from the protocol, clients can't fix that (just look at the absolute mess that rooms are). And still no support for custom emoji or stickers. Oh, and joining large rooms can still take hours.

toomanybeersies 5y ago
> And still no support for custom emoji or stickers That sounds like a feature to me.
- zaarn 5y ago
  Well, for my use cases it's required. If you run your own matrix home server feel free to ban it but for me that is an essential feature.
  - alexvoda 5y ago
    I can understand that it is a desired and important feature. But please explain how it is essential.
unicornporn 5y ago
> The Terrible UX is in part from the protocol, clients can't fix that (just look at the absolute mess that rooms are). Please explain.
- zaarn 5y ago
  Rooms don't form a cohesive set of channels that one can join, rather the group together a bunch of channels. If I, for example, setup a #rules channel in a community room, then I cannot ensure that users are reading this channel, which contains vital information about the operation of the community. Same for announcement channels for events. Instead of people joining a server community, they join a bunch of bubbles formed by the people using only subsets of the channels, without being able to direct the overall community. This is poor UX for both the user and the community operators.