Or continue using slack, but correctly.

We dont have offtopic in ours. We do have a #random chat, but its very infrequently used. Instead of zulips revolutionary tags, just use the slack threads.

Zulip wont save you if you're drowning in Slack messages.

We use Slack in a similar manner and the signal to noise ratio is extremely high. Some of our channels are key components of workflows. It's extremely easy to seek help or share information like links or code snippets. We're also very responsive, since it's always running on our workstations, laptops and phones. We'd probably frown on anyone treating it like a social media platform, though we do use it to let off steam once in a while.

Zulip does save you from drowning in messages! Instead of going through all the messages, one just have to go through Topics and consume messages only from topics they are interested in. This is so much efficient compared to a chat system without topics :)

Slack also has channels.

Topics are not the same as channels. In Zulip each conversation in a channel would have a topic. A channel would be a collection of topics. You can ignore the topics you are not interested in and focus on topics that are relevant. So for catching up all you need to do is go through the topics in a channel instead of going through all the messages.

https://imgur.com/UMBuOuh

Just the same as I can ignore threads in Slack which I have no interest in.

Its not the tool which break communication, its people not following rules. If people follow the "Use threads at all times" rule, slack is totally working fine. If people dont use it as their social media platform or keep their random thoughts to #random, there's no problem. It feels a bit tone-deaf to promote your tool in a thread about unproductivity caused by chat tools.

> It feels a bit tone-deaf to promote your tool in a thread about unproductivity caused by chat tools.

The entire article was written to promote their tool Nuclino.

>> All of our team's work (including the writing of this article) happens in Nuclino, and even though it's a real-time collaboration tool, most of it happens asynchronously. Without the expectations of an immediate response, our team is free to focus on our work, reconnecting later to respond.

I don't see any reason why one can't suggest an alternative product that solves the issues of synchronous chat apps just like the one mentioned in the Article. Zulip is an asynchronous tool just like Nuclino.

> Its not the tool which break communication, its people not following rules. If people follow the "Use threads at all times" rule, slack is totally working fine.

Eaxctly! People don't follow rules. Thats why Slack threads are hardly useful. On the other hand in Zulip people always create a new topic for a new conversation since that's how the tool is designed!

In my experience, Slack threads are absolutely horrible. I tend to miss that there's discussion on a thread for hours because it's almost "out of band" to the rest of the communication.

What's the difference between a Zulip topic and a Slack channel? Are topics inside a channel?

Yup. Zulip has channels just like Slack. A channel is comprised of topics. When someone want to start a conversation they create a new topic. If they want to just join an existing conversation they reply back to the existing topic.

You can see a live demo by visiting our community server at https://chat.zulip.org/

Thanks! I guess I should have bothered to read your other reply but didn't notice it :)