Threads are probably a good idea, but as many people have pointed out I still have to find an app that have a good implementation of them. Most of my experience

Threads are probably a good idea, but as many people have pointed out I still have to find an app that have a good implementation of them. Most of my experience is with Slack so maybe Twist/Zulip are better at this. * I hate threads in direct messages. Please, Slack, just give people a nice way to quote messages instead - which in my experience is mostly what people want. Right now it's a mix of copying a message and adding ">", sending a message as a thread with the "also post in the channel" flag or sharing the message and adding your reply there. I've had persons randomly pick one of my messages and then start a thread on top of that in direct messages, loosing context, but I'm not going to blame slack for that (but still, give me a way to disable threads there!) * They work great in big channels (hundreds or thousands of people - think channels like #rust-interest or similar), but then inevitably someone will reply outside of the thread, triggering other people to comment "reply in the thread" (modern "don't reply to this email!" in a reply all) or react with that damned thread emoji. A channel should have some way to "enforce" conversation by thread - offer tooling to move messages in threads and split threads, and make it slightly harder to accidentally post outside of a thread (maybe a different button, a confirmation message, or enforcing some style in the message. I'm sure nothing will 100% work after seeing people use @here and @channel and completely ignoring all the warnings, but still). * They are... meh in medium channels (team sized ones, thing 5 to 20 people), mostly because it's a pick and mix of people that want to use them and people that ignore them. This would at least improve if we had tooling to merge and slice threads, so that someone could at least try to enforce a style. But also from my experience it doesn't really matter too much, because not a lot of conversations will be happening there at the same time. * Thread discoverability sucks, you get notifications but then they're tucked in a single "thread" pane. That should be collapsable and show your recent threads, with individual notifications. * Using threads sucks too, you can either open one and lose context on everything else, or open one in a small sidebar, where posting more than 3 lines of code will fill it up and it's completely unreadable anyway. Having tabs or opening the thread in-line would be so much better. /rant