At first we used an internal IRC server, and only the ops team used it.
Then we switched to ejabberd, and got a little buy-in from other people in the company, but not very much.
The front-end team set up their own chat server without telling IT, and IT asked them what they actually wanted. Turns out, emojis and gifs.
When we switched over to Zulip, finally everyone used it. It meets our security requirements (no access without an existing account, https enforced), it meets the usability requirements (web client, Android client, iPhone client, emojis and gifs), and it doesn’t irritate the ops team.
I’m curious what client was being recommended to people for use with ejabberd. The client make the experience much mre than the server.
Almost everyone used Pidgin or its predecessor.
Man, it sucks Pidgin (and the XMPP ecosystem itself) calcified so badly.
Our decision tree was almost identical to yours, without the ejabberd detour and we use Mattermost, because it comes with Gitlab EE, otherwise we would probably use Zulip.
Do you know what it was that the front-end team was using before the Zulip switch?
I don’t recall; it was in use for about a week before IT asked them to stop it and tell [IT] their actual requirements.
I’ve said this before, but Zulip is one of the few web apps  that has decent typing latency and message send latency. I’ve had to use Slack on occasion and it always feels so slow and janky to me. And I’m using like a full tower desktop, not even a laptop.
GMail used to be fast but now it is slow. Part of it is using Firefox, but I don’t want to give up on Firefox.
So far I’m very happy with Zulip! Some new users have problems seeing the thread structure and figuring out how to start new threads, but that is a solvable problem.
 I don’t really consider lobste.rs a web app, more of a web site, but it’s doing well too!
I really start to like Zulip. Raph is using it for Xi, Piet and all his other projects that I like to lurk in. I really came to like the threading approach, since I can’t follow the chat all day long. Follow up on topics I am interested in is so much easier than compared to Discord or Slack. Arguable it makes free-form discussion a bit more tricky, but for Open Source projects it might be my go-to in the future. Really curious what other people’s experiences are with Zulip.
I am a huuuuuge fan of Zulip. I used it extensively in the Rust community, and in one company of ten-ish people, and it was markedly better for these use cases than slack, discord, irc or gitter.
I like Zulip’s threaded design, but, honestly, I find Slack not so bad as long as your team makes heavy use of threads.
I’ve started using Zulip for my own community (Building a Memex), and enjoying it so far. Topics/threads feel like it’s a knowledge database, not just discussions
I’ve been meaning to try Zulip - the fact it’s not another ircslackord clone, but instead has its own model is interesting.
My employer used to use HipChat, and I was envious of Slack. Now we use Slack, and I’m envious of Zulip. I don’t have any hope of being able to convince IT to change, though.
Could be worse. You could have to use MS Teams. It is so bad that I’m almost dreaming of switching to Slack.
Could be worse. You could use Slack and MS Teams and Yammer.
Similar experience to you.
One of the reasons I left my old job was that MS teams was so awful and mandatory.
Now I use slack at work and sit in envy of Zulip.
“Could be worse”, I remind myself.
Considering Slack’s per-seat pricing, I think Slack is far from building an empire that will stand the test of time.
Czech Pirate Party, about 700+ active users.
It’s sometimes bumpy, but still the best in class.
/me goes back to his 8k unread messages.