3 ms·

>If you wait for a long time to reply to a message on chat, then the discussion thread is already spread in the history of the chat room and messages back and f

>If you wait for a long time to reply to a message on chat, then the discussion thread is already spread in the history of the chat room and messages back and forth interleaved with many additional messages that are not related is not helpful. Use zulip - https://zulipchat.com https://zulipchat.com . Opensource. Designed for threaded context.

cortesoft 8y ago
I mean,slack has threads, too.
- saagarjha 8y ago
  They’re just a usability nightmare.
- vishnu_ks 8y ago
  Yeah. But threads in Slack are secondary and are mostly meant for having conversations that people don't care about. Zulip has a much superior threading model. Each and every conversation is a new thread and has a topic. This model makes it extremely easier to catch up and participate in conversations. https://zulipchat.com/why-zulip/ https://zulipchat.com/why-zulip/
radus 8y ago
Also enjoy Zulip for their very explicit threading system.
gregmac 8y ago
The only threaded chat I've used is Microsoft Teams, and I came away hating it. One problem is that if you are trying to catch up on conversions, instead of just being time based, it's thread+time based, so while you can see which threads added messages while you were gone, it's not easy to actually read through them all. The other big problem I found was people inevitably "reply" by (accidentally) creating a new thread, which then splits the conversation. If you're participating in real-time and there's not many separate conversions happening this isn't a big deal: but that's opposite to the situation where threading is actually theoretically useful, and catching up on multiple split threads is the worst combination of everything. Maybe this is only really a problem with Microsoft's implementation, but I'm curious what other people have experienced?

3 ms·

>If you wait for a long time to reply to a message on chat, then the discussion thread is already spread in the history of the chat room and messages back and f

by sandGorgon 8y ago

cortesoft 8y ago
I mean,slack has threads, too.
- saagarjha 8y ago
  They’re just a usability nightmare.
- vishnu_ks 8y ago
  Yeah. But threads in Slack are secondary and are mostly meant for having conversations that people don't care about. Zulip has a much superior threading model. Each and every conversation is a new thread and has a topic. This model makes it extremely easier to catch up and participate in conversations. https://zulipchat.com/why-zulip/ https://zulipchat.com/why-zulip/
radus 8y ago
Also enjoy Zulip for their very explicit threading system.
gregmac 8y ago
The only threaded chat I've used is Microsoft Teams, and I came away hating it. One problem is that if you are trying to catch up on conversions, instead of just being time based, it's thread+time based, so while you can see which threads added messages while you were gone, it's not easy to actually read through them all. The other big problem I found was people inevitably "reply" by (accidentally) creating a new thread, which then splits the conversation. If you're participating in real-time and there's not many separate conversions happening this isn't a big deal: but that's opposite to the situation where threading is actually theoretically useful, and catching up on multiple split threads is the worst combination of everything. Maybe this is only really a problem with Microsoft's implementation, but I'm curious what other people have experienced?