> Zulip is much better than Discord or Slack for managing the firehose of busy communities. Or at least, a lot of people tell us that they prefer the user experience to everything else they've tried, after a few weeks of getting used to it. :)

Could you expand on this?

▲

tabbott 2 hours ago | parent | next [-]

Check out https://zulip.com/for/communities/ and some of the linked case studies; they explain it better than I'll be able to in a quick comment.

But the main reason is that the topics-based organization and ability for moderators to move/split conversations means one can read and participate in a community much more fully given a fixed amount of time.

▲

bo1024 6 hours ago | parent | prev [-]

Slack has basically one main hierarchy level (messages are grouped into channels) while Zulip has two, streams and topics. So you can create a stream for each project (say) and create a different topic for any given point that needs discussion about that project.

Kind of like if each slack thread discussion had a title and was discoverable from the left sidebar and didn’t get in the way of the other threads.

▲

crabmusket 6 hours ago | parent | next [-]

> didn’t get in the way of the other threads

But also, critically, if you want to, you can drop back to the "show me everything sequentially" view. Threads hide discussions away - which is good when you want to focus on something else, but bad when you can't remember where a discussion was.

▲

jwiz 4 hours ago | parent | prev [-]

From what I have read (not having actually used Zulip) it always sounded like the chats were threaded in the same way that mailing lists or newsgroups are threaded.

How accurate is that understanding?

	▲	crabmusket an hour ago \| parent [-]
		That seems like a reasonable comparison. I've thought of Zulip as halfway between IRC and a forum.