Having tried Rocket, Riot, and Mattermost before, it's of my opinion as well as everyone that I work with that Discord blows them away. It's so much more polished.
- Message threads
- Ability to share screens when multiple people are in audio conference
- ability to "draw" over the screen while sharing
One thing I wish slack or others had that discord has is ability to select FPS for screen share: when I'm sharing the screen or camera (showing a whiteboard) I usually care more that the image looks with better detail even if it refreshes once every 20 seconds. Almost all screen sharing always introduce compression artifacts.
100% agree on the other two, though. Encouraging people to make channels as needed helps the first, but for ephemeral discussions you wind up deciding between deleting the chat log, or living with a lot of "retired" channels. And being default opt-in for notifications makes Discord _way_ more noisy than Slack could ever be.
* Can't leave a channel (without custom bot shenanigans, which doesn't scale well to having a lot of channels).
* No control of notification sounds on mobile. All notifications get the same sound and there's no option to deliver quietly.
* No threading.
* Can't collapse embeds.
* No back/forward navigation. The closest it gets is in the quickswitcher it offers the last channel you were in, but that's it.
* Their support is awful. Everything except extremely obvious bugs get the response "please vote it up at feedback.discordapp.com", and even bugs often get that response.
* No "do not disturb" settings. If notifications are on, they're on 24 hours a day.
TL;DR: If Linux can obsolete Solaris, Riot can obsolete Discord/Slack. Come get involved and help :)
Assuming it goes dormant and unused (which it may not, but often does), do you have a policy for stale / unused username deletion or reclamation?
We're looking at fixing this in future via https://github.com/matrix-org/matrix-doc/blob/rav/proposal/r....
Meanwhile, if you want echelon as a username, go register a domain name, run a matrix server on it, and you can have @echelon:echelon.xyz or wherever. Try not to get sued by five eyes though ;P
1) your "hey nice strong password" tooltip parks itself directly over the confirm password field so you (I) don't get to see it at all.
2) google captcha? ...really?
Yeah, that's not how it works, and you know it.
You are also implying that something changing and adding new features fast is good, and that's not true, either.
>If Linux can obsolete Solaris, Riot can obsolete Discord/Slack.
Jabber was also going to obsolete many things, and look at it.
- Have a bot invite everyone in the group to every room and kicks them out if they leave (noisy, not everyone needs to be in every room)
- Have everyone in the group use the same homeserver, make rooms public and non-federated (defeats much of the purpose of Matrix, doesn't let you invite people from outside the org as one-offs)
I think some of the future plans for communities would solve this?
Anyway, Matrix right now is great for both small private chats and FOSS projects; in the former case you can just handle access ad-hoc, and in the latter case the rooms are public anyway. It just seems a bit lacking at the moment for organizations that need private rooms.
It's not ideal, but shipping a mobile and desktop client that are literally incapable of displaying the same channels in the same order is also not ideal.
It was very strange because they had no idea what Teams was used for. They shared some literature that says the features are the same, but when asked to do simple tasks like use teams to coordinate the rollout, they didn’t know how to do it.
Kind of weird. My hope is that Microsoft eventually makes it usable since it’s basically free with other purchases. But then, Microsoft killed yammer and Skype.