Live data from Hacker News

Discord Launches Threads

blog.discord.com

101–110 of 233 posts

Re: Discord Launches Threads

#101
post #6

Is there really no better design for "aside" conversations than this? People lean on Slack threads too much, leading to a confused flow of conversation that makes it extremely difficult to piece together how the discussion was ended or resolved.

I’m always surprised by how practically every single opinion regarding personal communication is the opposite in hacker news to the mainstream opinion of my “real life” circles. Use of social networks, slack, emojis, messaging apps, sync vs async communication… Its not a criticism of any kind, mind you, it’s just very surprising to me.

Nah, lots of us here love threads. Threads was one of the reasons our large private friends-only Slack server didn't move to Discord. This has reignited that conversation, as we like Discord more for certain things, and threads were one of the things holding us back.

The difference is we just aren't really saying anything.

Re: Discord Launches Threads

#102
post #94

Off topic but here's another feature that really shouldn't take 2 years to implement - only showing "In game" status on some servers, vs the current all-or-nothing approach. https://support.discord.com/hc/en-us/community/posts/3600483...

Running two instances of Discord is not too complicated (at least on Linux) and might work well to separate your professional and gaming accounts. You only have to be careful of invite links, which will open in the first Discord you run.

Be aware that Discord treats this as a fraud indicator - the reason Ripcord does not support Discord multi-account is that it puts you at higher risk for a ban

Re: Discord Launches Threads

#103
post #31

Earlier quoted context omitted.

The lack of threads is something that made me not use Discord before (before they had the replies). There was simply no way to know who someone is replying to, or part of which of the multiple conversations in the channel is that message a part of

That's because it was designed to be a real time chat. When you're having a group conversation, there are no threads. You just keep track in your head what the topics are and who said them and then figure out how the next sentence applies. Discord was modeled after this interaction (and IRC, which was modeled after this interaction).

That might be the initial model, but it's not the current model. People use Discord for far more than real time chat. It's effectively replaced forums for many communities. While real time chat is still important, it's not the only use case.

Re: Discord Launches Threads

#104

The 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…

> abominations like slack - which hides streams of conversation behind a wall, making the UX terrible.

I'm not usually a defender of Slack but this is one of the things I _like_ about Slack threads. Typically in our rooms every discussion is a thread and if I'm not concerned with that particular discussion there's only ever one message and notification I need to dismiss. If I _am_ concerned with it I can opt in to reply notifications with two clicks.

Re: Discord Launches Threads

#105

Earlier quoted context omitted.

I guess I would have to use Flowdock to understand -- those gifs were confusing and unclear to me. I'm not sure what I was looking at. Personally I find slack threads perfectly usable and helpful for keeping things organized for the most part. What's the issue with them? I found them a revolutionary step forward in chat UX to be honest, something that had been missing for 20 years or more.

Some people - like myself - prefer to see all the messages go past and mentally thread them. It’s a skill I learnt from many years of irc use. Others prefer to click through and not think about thread content until they choose to. Also I’d rather not grab my mouse to see things.

> Also I’d rather not grab my mouse to see things.

I have not tried threads yet but I have been assured they are fully accessible via the keyboard only.

Re: Discord Launches Threads

#106

The 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…

> abominations like slack - which hides streams of conversation behind a wall, making the UX terrible. I'm not usually a defender of Slack but this is one of the things I _like_ about Slack threads. Typically in our rooms every discussion is a thread and if I'm not concerned with that particular discussion there's only ever one message and notification I need to dismiss. If I _am_ concerned with it I can opt in to re…

Same here, if you don't hide the thread then what's the point? Some technical discussions in our team board last for hundred of messages, without threads it would be really hard to follow the channel, especially with multiple discussions going at the same time.

Re: Discord Launches Threads

#107

The 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…

> abominations like slack - which hides streams of conversation behind a wall, making the UX terrible. I'm not usually a defender of Slack but this is one of the things I _like_ about Slack threads. Typically in our rooms every discussion is a thread and if I'm not concerned with that particular discussion there's only ever one message and notification I need to dismiss. If I _am_ concerned with it I can opt in to re…

I like how Slack hides threads. But I do have a few complaints.

I don't like that you can't come back later, select a bunch of messages or threads and say "Group into a thread" to clean up people not using threads.

Also I kind of hate when it's a week later and someone responds to a thread and you get pinged, but can't find where you got pinged from without clicking the dynamic group to see all thread activity.

Also, it really annoys me that threads open on the right with the text entry on the lower right when toast notifications on Windows pop up on the lower right, too. Great, now whenever someone replies I get a toast popup blocking me from seeing what I'm typing. Thanks, guys. Sure, that only happens on one monitor, but that's also the same monitor that I want my toast notifications and my Slack to be on because it's where I'm often looking.

Re: Discord Launches Threads

#108

Earlier quoted context omitted.

Man, I wish Slack would implement Discords "reply" feature that automatically quotes the post and @mentions the poster.

I think it has it, it's just called something else.

Yes, the "share message" feature accomplishes roughly the same in a less seamless way.

Re: Discord Launches Threads

#109
post #6

Is there really no better design for "aside" conversations than this? People lean on Slack threads too much, leading to a confused flow of conversation that makes it extremely difficult to piece together how the discussion was ended or resolved.

I’m always surprised by how practically every single opinion regarding personal communication is the opposite in hacker news to the mainstream opinion of my “real life” circles. Use of social networks, slack, emojis, messaging apps, sync vs async communication… Its not a criticism of any kind, mind you, it’s just very surprising to me.

I have some issues with Slack threads but use them a lot, appreciate them, and so far haven't seen a better solution (even in this thread).

HN always presents a lot of reactionary positions to anything.

Re: Discord Launches Threads

#110

Earlier quoted context omitted.

I guess I would have to use Flowdock to understand -- those gifs were confusing and unclear to me. I'm not sure what I was looking at. Personally I find slack threads perfectly usable and helpful for keeping things organized for the most part. What's the issue with them? I found them a revolutionary step forward in chat UX to be honest, something that had been missing for 20 years or more.

Some people - like myself - prefer to see all the messages go past and mentally thread them. It’s a skill I learnt from many years of irc use. Others prefer to click through and not think about thread content until they choose to. Also I’d rather not grab my mouse to see things.

> Also I’d rather not grab my mouse to see things.

Use the up and down arrows to navigate to the message you want and hit T to switch to the thread side view. Similarly, you can do the same to find your own messages and use E to edit them.

Post reply on HN