Discord Launches Threads
201–210 of 233 posts
Re: Discord Launches Threads
#202Servers have an obscene amount of channels, while IRC has a single channel per topic, and sometimes has one or a few more (ubuntu, for example).
I honestly have a hard time using discord because of that. Discussions are atomized. Some channel are just pointless and often silent. The notification system is stupid and you just mute everything because of it (the tray icon is always red while you have nothing to read, and you are not going to scroll all channels you're not really interested in).
Oh yeah, and displaying the user list is pretty pointless when there are more than 40 users. Just my opinion.
I just keep a very small amount of servers.
Re: Discord Launches Threads
#203The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
I actually feel that MS Teams is the best thread implementation (I haven't used Flowdock, but I have used Zulip). The app performance is a little slow which makes it feel slightly clunkier to use, but the UX for a normal Team channels makes everything be in a thread by default, and makes it completely intuitive.
Re: Discord Launches Threads
#204Earlier quoted context omitted.
> But first I had to add a new role to grant myself those permissions Assuming you're an Administrator, it's covered by that.
They aren't. Its a common system to only have the server owner and maybe 1 or 2 other people with the administrator permission. I personally run a 5k user discord with only me as the admin, and like 90 mods who can do varying levels of things. Why discord didn't make it default to on for people with manage_messages i don't understand.
Otherwise they would have enabled the feature and defaulted it to off. I found out that we had threads enabled when someone created a thread.
Re: Discord Launches Threads
#205Element (Matrix client) also announced that they will be adding threading soon. [1] [1]: https://matrix.org/blog/2021/07/27/element-raises-30-m-to-bo...
Re: Discord Launches Threads
#206The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
But the core design with threads is a killer feature and prevents migration to anything else.
Re: Discord Launches Threads
#207Earlier quoted context omitted.
It wouldn't be a problem, except that Discord takes over your fucking computer and doesn't let you sign into different accounts via private browser windows when you have the client running Another problem with Discord is that its anti-spam measures are making it harder and harder to create an anonymous account There's no point in having an anonymous Discord account if you have to use the same account for everything i…
> doesn't let you sign into different accounts via private browser windows when you have the client running What do you mean here? I have multiple discord accounts that I have logged in at once. One on the client, one in browser window, and another in a private window, working just fine. > Another problem with Discord is that its anti-spam measures are making it harder and harder to create an anonymous account Haven'…
It seems this has somehow changed. Historically, the web app connected to the webserver of the locally running client, so it was impossible to be logged into more than one account on a device with native app running.
Re: Discord Launches Threads
#208Re: Discord Launches Threads
#209The ideal thread implementation is in Flowdock (which not many people have heard of or use), but it's really the best of both worlds. Everything is a single stream of messages, and you can optionally group things as threads. There is a really nice blending of the two. Here's their implementation and you can see how well this works in practice. http://blog.flowdock.com/2017/08/31/the-1-customer-request-h... Far far be…
So I decided to do a search on Flowdock, turns out it is very old. And they have been down for two days [1] last year. Their last blog post are from 2018. [1] https://news.ycombinator.com/item?id=22945633
Lack of competent engineers in the product might also explain the extended downtimes last year. One of them apparently included a full-fledged database corruption where all conversations for a day or so were permanently lost.
I know at least one organization that is so deeply ingrained and accustomed to Flowdock that they haven't even considered migrating to Slack. I, too, still think that Flowdock is a superior product to Slack for the core chat feature. Adding simple video-conferencing would pretty much bring it up to speed with the modern day.
Re: Discord Launches Threads
#210The time limitations is just sad. Seems like the UX is pretty good but having a 24 hour auto-archive just makes me apprehensive to ever use them.