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

121–130 of 233 posts

Re: Discord Launches Threads

#121

Post by adrian17 »

dan_pixelflow wrote: post #69
adrian17 wrote: post #41

These look like a weird mix of Slack threads (temporary (though not enforced in Slack), written in sidebar) and Zulip threads/topics (named, available in the channel list), though... with downsides compared to both (for example, you can't forward messages to original channel like you could on Slack). Feels a bit awkward, but time will tell. My main concern right now is with discoverability and moderation - it seems a…

As a Discord moderator (discord.gg/wilbur, 310k+) who's used Threads for a few months now while testing, there's a specific Threads button that lists all open threads - even private ones, although behind a toggle - and that works pretty okay. Most large servers only use Threads internally within staff teams, not in the wider general channels yet, though!

> there's a specific Threads button that lists all open threads

I can see there's a Threads button next to the search bar, but it appears to be scoped to the channel I'm in; I don't see a way to see threads across all channels.

Re: Discord Launches Threads

#122

Post by pixelmonkey »

binarymax wrote: post #28

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…

Indeed! So good to find someone else who had this experience. We went from Flowdock => Slack on a fully distributed team of ~20 engineers, total staff size of ~40. Flowdock threading was night-and-day so much better than Slack threading. It was such a stark difference, everyone noticed. What's so maddening about this is that I'll bring it up to anyone who will listen, and they'll think I'm just nostalgic, or a curmudgeon against all new things. But no, Flowdock simply did threads better. And you had to use both, for awhile, on real teams, to "feel" the difference. (Screenshots can't really convey it.) If you were on a scaled team using Flowdock before adopting Slack, it would have been totally obvious to you.

Tweeted about this here:

https://twitter.com/amontalenti/status/1263317861537402885

Nice to meet a fellow traveller!

And yes, to the point of someone else on this HN thread, the closest thing to Flowdock threads on the market today in a semi-popular chat product is Zulip "Topics", as described here: https://zulip.com/help/about-streams-and-topics -- the difference is that Zulip forces threads to be labeled (similar to an email subject: line) whereas in Flowdock, all threads were anonymous, given a thread-id (permalink) automatically, and also automatically color-coded.

Re: Discord Launches Threads

#123

Post by naavis »

kowbell wrote: post #65
kowbell wrote: post #61

Earlier quoted context omitted.

> Threads make it harder and weirder for people to chime in halfway through or to catch up on what people have been saying I’m of the completely opposite opinion. If I want to contribute to a prior discussion that happened a few minutes ago but another one is taking place now, then we have two separate conversations in the same linear chat stream. With a thread, I can respond to who I want without interrupting anyone…

Forgot to mention: at my job, Slack threads have been super useful. Three or four people can discuss one topic in an open channel (so others can join in and we can search history) without spamming notifications against everyone else. E.g. someone could put a message in #engineering about a bug. All the engineers get that notification so anyone who knows more details can chip in immediately. They then reply in a threa…

Exactly, this is how we use it too.

Re: Discord Launches Threads

#125

Post by orliesaurus »

binarymax wrote: post #28

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…

+1 Flowdock - was using it back in 2014 and it had the best threading experience of all apps!

Re: Discord Launches Threads

#126

Post by zippergz »

afavour wrote: post #104
binarymax wrote: post #28

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…

Yes, this is exactly what threads are for. To get a side conversation out of the way.

Re: Discord Launches Threads

#127

Post by zippergz »

whall6 wrote: post #90
aerovistae wrote: post #82

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.

One thing that I don’t like is that I have to click a checkbox every time I want to submit a reply to a thread to the channel that the thread is in. Not everyone in the channel is notified in the same way when additional replies are made within a thread within the channel.

Which, indeed, is the point. Threads are primarily useful in very busy channels with multiple conversations happening. The point of a thread is to get the conversation out of the main channel so it doesn't disrupt other discussions. If you want every message to go to the main channel, just post it there, not in a thread. IMHO that checkbox shouldn't even exist.

Re: Discord Launches Threads

#128

Post by VRay »

cjsawyer wrote: post #83
ghostpepper wrote: post #79

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

I’d gladly share that info with my gaming friends, but on not on professional/work servers

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 in your life. (Reddit and Facebook have the same problem as well)

Re: Discord Launches Threads

#129

Post by rockostrich »

leppr wrote: post #108
DoctorShenan wrote: post #64

Earlier quoted context omitted.

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.

It's less "seamless", but also more flexible. The Discord reply feature only works within the same channel while you can share slack messages anywhere, including in threads by linking. Linking to discord messages works, but there's no inline preview.

Re: Discord Launches Threads

#130

Post by MrStonedOne »

ad404b8a372f2b9 wrote: post #111
MrStonedOne wrote: post #95

Fun fact: They granted create threads to everybody by default but granted manage threads to nobody by default. So we had moderators who could delete channels, delete create and modify roles and role permissions, and delete messages as well as ban/kick users, but couldn't manage or delete threads. "public threads" show up in the main channel list to everybody as a sub channel, and everybody had permission to create an…

When did the feature appear for you? It hasn't appeared yet in my channel.

it was randomly handed out to 10% of servers today.
Post reply on HN