Comment by dijit | Hacker News Reader

Comment by dijit | Hacker News Reader

I moved my company over to Zulip a while back and while I'll admit that it's not quite as polished as slack (the mobile app freezing and having a mildly different UX/features for example) -- it is a lot easier to follow conversations and topics.

It takes about a week to get used to, then people don't want to go back.

Bonus: it can be hosted for free (incl. SSO), though I take the path of paying the authors for their hosted version.

I really don't think I'll go back to Slack; Especially as they're owned by Salesforce and I suspect even more lockin in future and especially rent-seeking behaviour- which always comes from these large acquisitions. (people should be mindful of lock-in for those reasons in my opinion).

I also get massively tilted when non-optional changes to clients happen, like when they completely broke markdown formatting for their style bar, yet still had some markdown formatting enabled which messed up your messages randomly; like not being able to exit code blocks. >_<

I agree about not wanting to leave Zulip. I have to use Slack for work and I miss Zulip every day. On Slack, most of the time I can't find messages I just read. It's bad.

Also, I thought I was the only one who couldn't exit code blocks. The fact that that happens makes me irrationally angry.

If I don't remember what thread or channel I saw a message I hit the shortcut keys to get to the search bar and search for the sender using "from:@username".

That works well when I remember the sender, but I don't always notice who sent it :(

In those cases I go back in the history of chats that I visited with either CMD+[ or the dedicated "clock" button

Wait, what clock button?

EDIT: Holy shit, thank you!

You're welcome! Notice that you can go also forward in the history with CMD+] and If you happen to have back and forward buttons on your mouse (like an MX master) they also work ;-)

I do that too, thanks! Alt+left/right arrow works too, as normally for the browser.

> (the mobile app freezing

out of curiosity, is there a GH issue for that behavior? that sounds like a very straightforward "don't do IO on the UI thread" fix but if they don't know about it, I doubt they're looking for the fix

I haven't seen it, but it's so ubiquitous that I can't imagine it's not happening to anyone else.

i think the biggest lock-in factor would be integrations between github and all of the other 3rd party services

Reply on news.ycombinator.com