What I'd prefer is the Twist-style threads (Zulip may also have them), where every room/channel must contain only topics/threads, and those topics have a title/description, and any messages in them are 1-level (no nested threading). It looks like this: #office [room/channel] * Lunch [thread/topic] - Anyone wants to grab lunch today? [message] - Sure, I'll join! [message] - Me too! [message] * Printer doesn't work [th…
This is kind of what you get from Slack's threads — if everyone always uses the "also share to channel" option in the thread, and if everyone also make sure to otherwise never post directly to the channel. Which is impossible to enforce, of course.
I feel like, without such a braided view, it'd be very hard to follow several threads at once, if you were e.g. helping multiple people in a "support" channel, with each conversation being a thread. Once you navigated into a thread, you wouldn't be able to see activity in sibling threads until you navigated out. You'd know that something happened, but you wouldn't be able to glance at the content to tell if it's more urgent than your current conversation. (You could rely on app toast notifications, but you might miss these if you glance away for a moment.)