4 ms·
We use zulip at work (yes, heavy geek influence:) ). Nothing except social pressure prevents people from misusing topics. It happens to all of us, when a diffe
by usr1106 4y ago
We use zulip at work (yes, heavy geek influence:) ).
Nothing except social pressure prevents people from misusing topics. It happens to all of us, when a different thread gets spawned during a discussion. Sometimes when someone does not know where a question or bug would belong to. But you can move the messages in question to a suitable topic (existing or new) at any time. That used to be a bit buggy in the past, but has been working smoothly for a couple of releases.
Within the same zulip stream everyone can do it (in theory causing edit wars, but it has never happened in our company). To move it to a different stream, you need to be admin. That's sometimes a bit weird, but our admin is quick to do it when discussions went offtopic.
Edit: I can't answer why it was worse in Slack. Luckily I haven't had to use Slack for 4 years. I only remember that it was much worse. Wasn't it so in Slack the user replying explicitly needed to select a threaded reply (and few did so). And even if they had done so, the one coming to work 8 or 24 hours later needed to look through everything (or nothing) because the (possibly threaded) messages had no topic?