Live data from Hacker News

Zulip 3.0: Threaded Open Source Team Chat

blog.zulip.com

11–20 of 134 posts

Re: Zulip 3.0: Threaded Open Source Team Chat

#11
I noticed the changed logo and favicon today. I’m not fond of it yet: I find the discontinuity in the middle of the Z crossstroke surprisingly disconcerting. At large sizes it might work out OK (though I’m not convinced, it’s still feeling unbalanced somehow), but at small sizes it really doesn’t work.

Furthermore, they’ve changed the style of the “number of unread messages” badge on the favicon so that it’s bigger and less… neat, is probably the right word, having gone for the “write the number in a normal sort of a font on a semitransparent white background and sit that atop the original favicon” rather than writing the number in what’s essentially a small bitmap font without needing the semitransparent white bit; and given that style, it looks quite terrible on a dark background, which my tab bar is. It ends up looking like the icon is just a number on some indistinct mess, with no real substance of the logo left visible, where before it was a clearly-visible small number on a clear and distinct Zulip logo. It’s unfortunately fundamentally impossible to pull off the style they’ve changed to—you must know whether it’s going to be matted against a dark or light colour for it to work, and the web doesn’t give you that. (I really wish it did. Sure, there are a couple of workarounds like using the (prefers-color-scheme: dark) media query to guess that the tab bar is probably dark, and that if that doesn’t match it’s probably light, but that’s still wildly inaccurate and insufficient. It’s a big enough deal that I’d like browser manufacturers to come up with something.)

In all this I do say that I’m not fond of it yet. It’ll doubtless feel more acceptable after a few days. But comparing my reasons for disliking it with other occasions when I’ve not liked change (either at first or forever), I don’t think it’s going to grow on me as much as many do.

Re: Zulip 3.0: Threaded Open Source Team Chat

#12
post #4

Threads are one major reason I like Zulip over Slack, but speed is another. I usually have two different instances open on my browser with no problems, and one of them has dozens of conversations going on at once. Zulip is also one of the only apps I put on my iPhone, and it's straightforward and unobtrusive. For some reason when I use Slack, the keys feel mushy. I think they're doing so much stuff in the background…

They are the primary reason to use Zulip. In this way, Zulip is more of a Teams competitor than it is a Slack competitor. I, frankly, cannot stand threads. I want a chat room, not a realtime forum. I understand why people would like that, but it still bothers the shit out of me. I work for MS so we have to use Teams, but I'd prefer opt-in to threads vs. threads by default. I fully understand and accept that my way is…

Can't you just make a single "general" room and talk in there? Have you ever used Zulip? Your objection puzzles me a bit because I can't see how it's a problem, since your use case is trivially supported.

Re: Zulip 3.0: Threaded Open Source Team Chat

#13
I can't recommend Zulip enough. It made remote communication many times easier, it's a dream to use because it's faster than Slack (though that bar is so low you have to dig to find it) and Riot, and its keyboard navigation is second to none.

The mental model might take an hour or two to click, but you can think of it as Slack rooms where the only thing you can do is open new threads (can't post messages in the room itself, only in the threads).

I really really think everyone should try it, it's a big improvement.

Re: Zulip 3.0: Threaded Open Source Team Chat

#14

Earlier quoted context omitted.

They are the primary reason to use Zulip. In this way, Zulip is more of a Teams competitor than it is a Slack competitor. I, frankly, cannot stand threads. I want a chat room, not a realtime forum. I understand why people would like that, but it still bothers the shit out of me. I work for MS so we have to use Teams, but I'd prefer opt-in to threads vs. threads by default. I fully understand and accept that my way is…

Can't you just make a single "general" room and talk in there? Have you ever used Zulip? Your objection puzzles me a bit because I can't see how it's a problem, since your use case is trivially supported.

Yes, I've used zulip - every single comment spawned a thread or responded to a thread. Users weren't used to responding to a thread, which meant we had threads of single comments constantly. I'm puzzled that you're puzzled. I thought this was the way Zulip worked. It was about 2 years ago, at any rate. Did it change since then? If so, that's exciting in its own right.

Re: Zulip 3.0: Threaded Open Source Team Chat

#15
I am looking for something to replace XMPP with our team; I wonder if Zulip could be the one. I do like the thread idea.

Does anyone know if there is a CLI client, and if E2E encryption is possible with Zulip? It does not seem like these are built-in, but maybe someone built these as add-ons somewhere.

I love XMPP, and OMEMO, but Profanity, and Conversations have some weird quirks when used together that we would rather avoid. And while we would love to just move to IRC, and WeeChat, lack of E2E encryption is a deal-breaker.

Re: Zulip 3.0: Threaded Open Source Team Chat

#17

I am looking for something to replace XMPP with our team; I wonder if Zulip could be the one. I do like the thread idea. Does anyone know if there is a CLI client, and if E2E encryption is possible with Zulip? It does not seem like these are built-in, but maybe someone built these as add-ons somewhere. I love XMPP, and OMEMO, but Profanity, and Conversations have some weird quirks when used together that we would rat…

There is a Zulip CLI client - https://github.com/zulip/zulip-terminal .

Re: Zulip 3.0: Threaded Open Source Team Chat

#18
A group of us in the Julia open source community have been trying to migrate to Zulip [1] from Slack. There's a lot of resistance from some community members, but those of us who made the switch are quite happy.

The topics model is fantastic, having proper markdown and LaTeX support is also killer.

The development team for Zulip is also really responsive and friendly. Coming from Slack, it was a breath of fresh air to be able to make an issue on their GitHub issue tracker and have fast, friendly thoughtful replies and quick action.

[1] https://julialang.zulipchat.com/#recent_topics if you wanna check it out

Re: Zulip 3.0: Threaded Open Source Team Chat

#19
Unrelated question - I went to chat.zulip.com in the browser and signed up. Scrolling through the messages (pixel xl2) is incredibly laggy.

If I were to build a similar UI on some project, what's a good way to ensure good scrolling performance on the web?

Re: Zulip 3.0: Threaded Open Source Team Chat

#20

Earlier quoted context omitted.

Can't you just make a single "general" room and talk in there? Have you ever used Zulip? Your objection puzzles me a bit because I can't see how it's a problem, since your use case is trivially supported.

Yes, I've used zulip - every single comment spawned a thread or responded to a thread. Users weren't used to responding to a thread, which meant we had threads of single comments constantly . I'm puzzled that you're puzzled. I thought this was the way Zulip worked. It was about 2 years ago, at any rate. Did it change since then? If so, that's exciting in its own right.

Hmm, that sounds like something was going wrong, threads don't just spawn, you have to create them, and a thread with a single comment kind of defeats the purpose.

Oh, were you editing the subject every time you commented, maybe? That's not indicated, you only edit the subject when you want to create a new thread. In our use case, threads were relatively infrequent and specific to a topic, e.g. "middle name database migration", and that's where the discussion for that happened.

Post reply on HN