The thing that really impressed me the most about Discord, was the zero-cost of entry to a (air-quotes) “server,” once you have logged into the Discord system over-all.
It’s extraordinarily trivial to get from a link on someone’s page in a web browser, to being in the midst of a virtual discussion on a Discord server, with hardly anything more than a tiny tiny speed-bump.
That’s exciting to me.
It’s exciting because whenever you have to go through a process, like creating a username and password, and then going to your email to click on an authentication link, and then give your date of biiiiirth, and yadda yadda yadda yadda, – it’s like two seconds into that and “nope nope nope” I’m turning around and going home.
“Oh, you have a Slack team?” 🥱 “That’s very nice.”
(The irony is that StarCommunity uses Slack.)
The reason we use Slack, rather than Discord, (and we seriously did consider Discord,) is because Slack has built-in permissions support.
We often have special-purpose locked channels, and if you’re going to do that with Discord, you have to specially create an environment and systems and bots and it’s not at all clear to us how to make it work.
Alex Schroeder: Yes, can confirm: the ease of use is amazing.
For me, Discord was really confusing after using [[Telegram?]], the best messaging platform out there. Discord is still good though, optional registration is amazing.
Lion, Discord has quite detailed permission capabilities without using bots. There’s that thing called roles, they are configured in server options by admin.
Oh, cool! I’ll look into roles.
Hm, I looked into it, and it looks like – it won’t really work.
What we frequently need in StarCommunity is the capacity to create channels, on the spot, that only say, 3 or 4 people are communicating in, and the capacity to pull in other people as needed.
With Discord, it seems that you have to make a separate role each time that you want to do this, put people into that role, create a hidden channel, and then specifically name that role for that channel as the only one allowed. That’s too many operations for a common situation. Furthermore, we need pretty much everybody to be able to do this, at will, and that seems nearly impossible to set up, with the Discord permissions system.