News for hackers. Stuff that matters.
Re:Zulip 5.0: Threaded open-source team chat by tfehring on Tuesday March 29, 2022 @04:39PM (#30848078)
For better or worse, I think Slack’s approach of opt-in threading is effectively the default at this point. If users’ (technical or otherwise) mental model assumes that messages can get sent to a channel, but the software only allows messages to be sent to a thread, that disconnect could result in lots of unexpected behaviors.

For what it’s worth, I personally prefer Slack’s approach over Zulip’s - I think threading is a really important feature, but requiring it for every message creates excessive and unnecessary friction.

Re:Zulip 5.0: Threaded open-source team chat by gilbertbw on Tuesday March 29, 2022 @05:21PM (#30848527)
Personally I’ve found the ability to move messages between / split threads (topics) helps a lot with this in Zulip. We moved from Slack, and those that struggled with threading there mostly picked it up over a few weeks.
Re:Zulip 5.0: Threaded open-source team chat by conradludgate on Tuesday March 29, 2022 @04:48PM (#30848161)
I think if you could type a message, and it could use some heuristic to determine a sensible thread title for you automatically, that would improve the experience quite a bit
Re:Zulip 5.0: Threaded open-source team chat by tfehring on Tuesday March 29, 2022 @05:08PM (#30848387)
Yeah, I think that would help a lot. I think I’d personally go a step further and make thread titles optional, I generally don’t think they add much value over just reading the first message in the thread.

Even with that change, though, I’d still rather have threading be opt-in. Not every message fits well into exactly one thread.