2 ms·
I agree that Discord and Slack has some bad sides, but for kinda opposite reasons than the author. There are so many discussions, QAs, tips&tricks etc. shared
by matsemann 7y ago
I agree that Discord and Slack has some bad sides, but for kinda opposite reasons than the author.
There are so many discussions, QAs, tips&tricks etc. shared on these chat rooms, that are impossible to find for those not a part of it. If it was discussed in a public forum somewhere, it would pop up in a search engine. I may have a problem with tool X and google for a solution, but since the discussion happened in some closed Discord server I will never find the solution someone else there has posted.
So kinda the opposite of the author's point about privacy: I prefer everything to be open and accessible. Hiding this stuff hampers the adoption without people realizing. I don't join a discord for everything I use, and often I'm not even aware that it exists.
An example I had a few weeks ago: Elm package repo died so I got some weird errors when building my project. Apparently lots of people were aware and knew about the problem and the status. But it was discussed in some Elm slack (I think), so for me not a member there I had no idea what was going on and couldn't find anything about it.
- sneak 7y agoPrivate things, like DMs and user IP/location, should remain private. Teams using Discord force their team participants to share this information with Discord to participate, who can then share it with whomever they want, with no legal recourse if they harm you as a result. Public things, like discussion and documentation, should be open and available. Teams using Discord have outsourced to Discord the decision of who is allowed to even read information that should be public. People who don’t ID themselves to Discord and agree to not sue them are prohibited from reading. It fails on both counts.