Hacker News Reader

Comment by pfranz | Hacker News Reader

I've heard Zulip is much better about threads, but in Slack there are some annoying things about them. Everything is crammed into the sidebar, so reading log snippets suck. Also, I noticed people will often post their initial message, then a @here with slightly more info in the same channel. I'm not sure where to begin the thread from. I haven't been able to intuit the rules for alerting people or uploading things like images into a thread.

View on HN

Zulip (and Zephyr) is indeed much better for threads. You can actually find them to use them later. In Slack, it's more like a side-bar, instead of a topic that you could come back to later and anyone throw into.

Whereas I used threads all the time in Zulip, they are really not great in Slack, and mostly just useful for reducing noise for off-topic discussion.

I could be misremembering, but I think Zulip let anyone attach a message to a thread, not just the original writer (I think because it identified threads by text match).

FYI for slack I see a button for "All Threads" or "New Threads" at the top of the left sidebar. Here you can see all your threads in full width glory (instead of crammed into the sidebar which I agree is annoying).

You're right. I don't know if this is a bad habit on my part, but I generally avoid "All Unreads" and "All Threads" because I'm focused on one thing at a time and want to leave unaddressed things unread until I can focus attention on them.

Reply on news.ycombinator.com