You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been playing with Zulip off and on for months (maybe a year or two?) but today I finally installed a desktop client and was impressed that you can point it at public orgs and don't even have to log in. It looks and works great. Here is the desktop app pointed at https://chat.zulip.org
"I guess one of our folks who joined recently, he started out as an intern, and then joined as a full-time team member, and he commented that he was surprised when he got added to kind of all our private company channels, just how little traffic there is in those channels. He was thinking that – when we were giving him feedback on things he was working on, maybe we’re like somewhere off on the side discussing that amongst ourselves, and then providing the summary version… He was like “Oh, wait… No, that’s not how it works.” I was like “No, no, no. Yeah. If we’re talking about how the product should work, we just talk about that in the open, and that way everybody can kind of understand the decisions, can contribute to the decisions…”"
They talk in the open at https://chat.zulip.org with channels for design, desktop, mobile, etc.
I guess I'll also mention that I switched Dataverse from Matrix to Zulip. The details are here:
Zulip has recently come onto the "transparent chat for open source projects" scene with a public access option: https://zulip.com/help/public-access-option
Here's the blog post announcing it: https://blog.zulip.com/2022/05/05/public-access-option/
I've been playing with Zulip off and on for months (maybe a year or two?) but today I finally installed a desktop client and was impressed that you can point it at public orgs and don't even have to log in. It looks and works great. Here is the desktop app pointed at https://chat.zulip.org
Some additional thoughts on Zulip:
The text was updated successfully, but these errors were encountered: