Honestly I found Zulip way too confusing. Am I the only one?
Zulip 3.0: Threaded Open Source Team Chat
31–40 of 134 posts
Re: Zulip 3.0: Threaded Open Source Team Chat
#32Unrelated 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?
Generally Zulip's scrolling and view-switching is very smooth and a ton of work has gone into it (my view is that if an app that you use all day isn't snappy it's going to waste tons of your time).
The short answer for how to make good scrolling performance (like any other performance work, really) is to profile, make sure you understand what's happening, and fix it. It can be hard to predict what makes things slow without doing so. (Fun fact: seemingly reasonable ways to use an emoji spritesheet with CSS can wreck scrolling performance).
Re: Zulip 3.0: Threaded Open Source Team Chat
#33Earlier quoted context omitted.
There is a Zulip CLI client - https://github.com/zulip/zulip-terminal .
Awesome, and it seems to be official as well. They could mention it on their website, even though it is still not considered stable. Now to look for E2E encryption support.
Re: Zulip 3.0: Threaded Open Source Team Chat
#34Threads 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…
Personally I'm finding it a bit of a nightmare, as just about every community I'm interested in seems to require a different tool to be installed. Same for work clients.
Worse than that, some communities are fragmented into different IM tool groups.
The plethora of IM and other tools needed to stay vaguely involved in the leading edge conversation in multiple communities is a right pain for usability.
What I really want is some way to see an overview of conversations in multiple communities I'm interested in and interact with them through that. A single tool would be nice, but some way of visually integrating similar tools would be ok as well.
I was pretty happy with Pidgin for this many years ago, as it worked with almost everything. But even then I needed Skype separately. I don't think libpurple is quite as universal now.
Matrix is an attempt, but by no means a solution.
Re: Zulip 3.0: Threaded Open Source Team Chat
#35Re: Zulip 3.0: Threaded Open Source Team Chat
#36I love the idea of this, but I’m trying to move my team away from synchronous communication. That tends to put us back in email, though that has its own problems. What is the asynchronous version of zulip? Forums?
Re: Zulip 3.0: Threaded Open Source Team Chat
#37Can you do screensharing and audio call in Zulip?
Zulip integrates with Jitsi Meet, so the video call button generates a unique Jitsi meeting link which everyone can join without installing anything or making an account.
This release removes Google Hangouts support (as Google killed it and rebranded it to Google Meet). Unfortunately, the Google Meet rebrand came with removing the API that was useful for third party tools like Zulip. I don't understand why they don't provide the brilliant API Jitsi has where you can just generate a URL containing a random meeting ID and everyone who clicks it gets the same meeting (which Google Hangouts did, at least if everyone was in the same G Suite team).
We also support Zoom (though note that Zulip Cloud is stuck in their marketplace approval process as it has been for months; supposedly it'll get approved any day now).
https://zulip.com/help/start-a-call
(And of course we're happy to integrate anything else that has a reasonable API)
Re: Zulip 3.0: Threaded Open Source Team Chat
#38I 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…
Like XMPP it supports federation, but Matrix is JSON instead of XML.
Re: Zulip 3.0: Threaded Open Source Team Chat
#39I 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 a…
For the number-of-unreads bit: might I persuade you to make an account on chat.zulip.org and come give that feedback there? That way we can perhaps iterate on variations of it and you can discuss those too.
Re: Zulip 3.0: Threaded Open Source Team Chat
#40Earlier 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…
> The good news is there are tons of options for people to choose what fits best for them! That's super exciting! Personally I'm finding it a bit of a nightmare, as just about every community I'm interested in seems to require a different tool to be installed. Same for work clients. Worse than that, some communities are fragmented into different IM tool groups. The plethora of IM and other tools needed to stay vaguel…