3 ms·
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 p
by bo1024 8mo ago
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 8mo ago> 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.
- folmar 8mo agoThe killer feateure is that it's very easy to move last $x messages to another topic, so if someone writes a short note that begins a conversation everyone is free to reorganize it, and also moving messages between threads is easy and nice.
- jwiz 8mo agoFrom 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 8mo agoThat seems like a reasonable comparison. I've thought of Zulip as halfway between IRC and a forum.
- bo1024 8mo agoNo, it’s not fully threaded like those examples (or HN). In a particular discussion, you can’t reply to a post in the middle and have your reply branch off from the main discussion.