This app is still in early alpha but I managed to spin it up yesterday and it seemed to work pretty well during my brief testing.
The github has been pretty active since the release yesterday. Note that this isn’t my project, just found the Dev sharing it on reddit yesterday
I don’t like Matrix because you can’t sort and categorise channels in a server. The most recently messaged in channel is always at the top. That’s not the UX I want, I want to be able to put things in places with intentionality.
That literally has to be a client option. Pick your favorite client with a receptive team and request sorting as a feature.
Exactly this, that’s a client quirk, probably Element in this case.
If it’s not supported by the protocol, how is an admin’s sorting of channels supposed to be pushed to the users in the server? It won’t work, it can’t be a client option. If it has to be a client option and it can’t, then it’s impossible.
I don’t understand what you’re trying to say. Matrix is the communication protocol between clients and servers. It can’t dictate how a client displays those communications. It would be like TCP demanding that webpages be laid out a certain way.
HTML and CSS are also protocols. But I think a better analogy is RSS. RSS carries information about the order of posts, which clients can use however they want. I think that’s the right way to do this feature.
How does my client know to use dark mode without the protocol knowing?!
Are you saying you want the moderators of a Discord server to decide whether users on the server use dark mode or light mode?
I’m saying you’re confused on how the technology works. There’s differences between the protocol, user account settings, user account preferences, and local client settings.
The protocol is how messages are sent and processed. User account settings are what your user is allowed to do and kept on the server. User account preferences are things that should be sent to your client when you log into it. Local client settings are things that the software you are running should know.
Your group arrangement should either be under user account preferences, or local client settings. This is not part of the messaging protocol.
I disagree. On Discord, channels are sorted and grouped by the server admins. This is good UX design because it gives every user on a server the same experience of the channels, and doesn’t require users to all replicate a bunch of the same work.
What you’re proposing as a solution is that every single user in a Matrix space is responsible for sorting and grouping all of the channels in the space that they’ve joined. That’s a ridiculous proposal because 99% of users aren’t going to go to that ridiculous effort, they’re going to be happy with the default settings. I think your idea is better than Matrix’s current setup, but it’s far worse than Discord from a usability perspective.
it’s so ridiculous that it’s what IRC clients and Slack does.
I’m sorry that I forgot to also specify that what you’re talking about could be part of the admin settings for the specific server, which is where that information should be, which again, is not going to be part of the chat protocol.
The Matrix protocol sends the channel name and icon from server to user client. It’s one extra field to add the ordinality. Two extra fields to add the category and ordinality. Adding your idea onto My idea so users can also reorder channels after the space moderator orders them would be ideal, but please don’t mistake My suggestion for the idea you came up with.
Someone just needs to make a discord clone on Matrix, can’t be that hard, right?
Already did, it’s called Commet.
deleted by creator