Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Discord Launches Threads

blog.discord.com

Post reply on HN
Print view View original

31–40 of 233 posts

Re: Discord Launches Threads

#31

Post by jedberg »

FalconSensei wrote: post #24
Grimm1 wrote: post #19

Earlier quoted context omitted.

I would be a bit slower on the hasty generalizations. I’m here on hacker news and I love using threads and am happy they’re coming to Discord there’s also multiple comments below this saying the same thing.

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).

Re: Discord Launches Threads

#33

Post by giglamesh »

TheJoeDonger wrote: post #5

Threads suck!

At my org, any given Slack conversation includes from two to six people. With that many participants, and given low volume, threads only present an extreme UX annoyance. I have to assume that the use case intended for them was high volume channels with lots and lots of users.

Re: Discord Launches Threads

#34

Post by lwn »

Oh my thread! I hope this doesn't go Slack.

edit: After my initial response (above) I was thinking I don't remember chat systems having 'proper' threads implemented, while forum software and commenting systems do have. Why is this?

Re: Discord Launches Threads

#35

Post by Ashanmaril »

This seems nice. I'm not a huge Discord user but one thing that always bugs me when I'm occasionally using it is when there's 2 topics of conversation going on at once. It especially happens a lot in help threads, where 2 people are needing help at the same time and people have to keep replying to the previous message in that conversation.

Though at the same time, it seems a bit weird that it's almost like a sub-channel? Does that mean in this scenario you'd have a whole list of threads down the side underneath the channel for every question?

I see people complaining about Slack threads but I personally find them perfect for what it needs to do. Creating a short thread from a message doesn't seem as big of a deal as what this looks to be doing.

Re: Discord Launches Threads

#36

Post by renewiltord »

css wrote: post #25
renewiltord wrote: post #20

Earlier quoted context omitted.

That looks identical to Slack's implementation to my eyes. If you don't mind sharing, what did you like better?

Slack threads don’t (or at least, didn’t; it’s been a couple years) show in the main message feed, they show when you expand the thread into the sidebar. In the feed, it shows the original message with an “n replies” text below it. In Mattermost, new replies show as normal messages in your feed with a bit of context for what they’re replying to, and clicking on the context expands the full thread in a sidebar. I find…

Ah interesting. I believe Slack does the former thing (displays as k replies) but not the latter. Thanks.

Re: Discord Launches Threads

#37

Post by rolleiflex »

ferdowsi wrote: 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.

The only other type of thread design I know of is Reddit-style threads in a chat app. The negative of that is that the threads cannot be directly incorporated into chat itself after creation because they become things of their own, just like Reddit threads, but the positive is massive: threads are entities of their own and they can be infinitely nested and referred to indefinitely into the future.

An example of this design is Aether. (Disclosure: I work on this, aether.app) If you have issues with Slack-style threads or curious about alternative solutions to this issue, it might be worth checking out.

Re: Discord Launches Threads

#39

Post by jjjgcddf »

css wrote: post #25
renewiltord wrote: post #20

Earlier quoted context omitted.

That looks identical to Slack's implementation to my eyes. If you don't mind sharing, what did you like better?

Slack threads don’t (or at least, didn’t; it’s been a couple years) show in the main message feed, they show when you expand the thread into the sidebar. In the feed, it shows the original message with an “n replies” text below it. In Mattermost, new replies show as normal messages in your feed with a bit of context for what they’re replying to, and clicking on the context expands the full thread in a sidebar. I find…

You might not have noticed but your link goes to the new design (in beta) of collapsed threads which are much more similar to Slack's and I think this has caused some confusion in this thread

It's worth noting that the design you prefer isn't being deprecated; Slack-style threads are being added as a user display option.

Re: Discord Launches Threads

#40

Post by [deleted] »

Ashanmaril wrote: post #35

This seems nice. I'm not a huge Discord user but one thing that always bugs me when I'm occasionally using it is when there's 2 topics of conversation going on at once. It especially happens a lot in help threads, where 2 people are needing help at the same time and people have to keep replying to the previous message in that conversation. Though at the same time, it seems a bit weird that it's almost like a sub-chan…

[deleted]
Post reply on HN