Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Zulip 3.0: Threaded Open Source Team Chat

blog.zulip.com

Post reply on HN
Print view View original

61–70 of 134 posts

Re: Zulip 3.0: Threaded Open Source Team Chat

#61

Post by hereisdx »

sdesol wrote: post #59
hereisdx wrote: post #44

Apart from a user, I am also a contributor to the Zulip project, for the last ~7 months. The community is very helpful and for getting started with open source development, I can't recommend a better place. You get really high quality code reviews, get to participate in meaningful discussions on features and the development goals of the project, and developers constantly share lots of knowledge in streams like #learn…

> The community is very helpful and for getting started with open source development That probably explains the healthy number of active developers for this project: https://imgur.com/XwhDHVZ Based on my simple analytics that looks at the time between a contributors first and last commit, I'm getting 50 active contributors, which matches up with many of the other popular open source projects I've indexed.

Also, that's just the server project. There are also clients like the mobile app and the terminal app, which have a whole new set of active contributors.

Re: Zulip 3.0: Threaded Open Source Team Chat

#62

Post by bovermyer »

tabbott wrote: post #57
bovermyer wrote: post #47

I would love to use this, but I don't manage any communities that aren't already married to either Discord or Slack.

FWIW we have been seeing a lot of larger communities that previously were deadset on Slack because "everyone knows it" importing their data from Slack in the last few months. Part of the reason is that Zulip's topics make it a lot easier for a part-time participant to use their limited time well (E.g. skimming or reading the conversations in most relevant to them in batch a few times a week). The Slack/Discord/IRC/et…

Awesome.

Well, I have no users because there's no community yet, but I did set up a Zulip (cloud) for my Iron Arachne project.

I plan on linking to it from the website's main menu.

Re: Zulip 3.0: Threaded Open Source Team Chat

#63

Post by isbjorn16 »

molsongolden wrote: post #25
isbjorn16 wrote: post #14

Earlier quoted context omitted.

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.

This is the case (and it's okay)! Every message (other than PMs) is within a topic thread which is within a stream. This can be structured by having ongoing social threads but users do need to know that they should respond to existing "broad topic ongoing" threads instead of creating a new micro-thread for every message. We structure the Streams into roughly: - company-wide announcements - org streams - team streams…

I bet that was the problem; we created streams for channels and vs. having a single stream with all the channels being threads inside of them.

Re: Zulip 3.0: Threaded Open Source Team Chat

#64

Post by rst »

hereisdx wrote: post #60
rst wrote: post #8

Earlier quoted context omitted.

You may not even need the app. Zulip on Android Firefox is a better experience for me than the app, personally. (Tho the web version was, oddly, severely laggy in mobile Chrome the one time I tried it, some time ago...)

Can you share what you did not like about the app? I would love to know what the users don't like so we can work on those areas.

The UI is somewhat confusing; also, it seems designed to give a view of particular, selected streams and topics of interest, and doesn't always seem to keep up even with those -- but volume on my server is low enough that I want "all messages", and if there's UI which does that reliably... it's not signposted well enough for me to find it before my patience ran out.

Re: Zulip 3.0: Threaded Open Source Team Chat

#65

Post by oehtXRwMkIs »

dTal wrote: post #48
eigenspace wrote: post #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 t…

That's excellent news. Being locked out of the community by virtue of it being hosted on a proprietary service, requiring a proprietary code blob to access, was one of the biggest sour notes I had coming to Julia. (Now if only discourse.julialang.org links would render without Javascript!)

Remind me of Rust with the added bonus of requiring a GitHub account to upload crates.

Re: Zulip 3.0: Threaded Open Source Team Chat

#66

Post by JoshTriplett »

The Rust community uses Zulip heavily; I'm on it every day.

Before I tried it, I was a little resistant to "yet another chat platform", and I didn't know how easily the threading model would work. Once I tried it, I got used to it very quickly, and started very much enjoying it. I'd highly recommend it.

I also think it works well with automation; bots can create threads, and do things in response to messages in those threads.

Re: Zulip 3.0: Threaded Open Source Team Chat

#67

Post by JoshTriplett »

stavros wrote: post #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…

> 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've used both Slack and Zulip, and I wouldn't describe it that way. Slack threads feel more "isolated" by default, hidden away from the conversation, and you have to go look at each one; a Slack channel where you can only create threads doesn't feel like it'd be as appealing a UI as Zulip. On Zulip, you can look at the entire stream to see messages from different threads in real-time, or you can look at just one thread and see only the messages from that thread.

Re: Zulip 3.0: Threaded Open Source Team Chat

#68

Post by rakoo »

jamesponddotco wrote: post #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 rat…

E2E encryption kinda breaks with the model of Zulip, ie a company or a project where everything should be visible by everyone even if they arrive after the conversation has started. You'll probably be better served by hosting your own instance and trusting everyone who connects to it.

Re: Zulip 3.0: Threaded Open Source Team Chat

#69

Post by StavrosK »

JoshTriplett wrote: post #67
stavros wrote: post #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…

> 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've used both Slack and Zulip, and I wouldn't describe it that way. Slack threads feel more "isolated" by default, hidden away from the conversation, and you have to go look at each one; a Slack channel where y…

Oh, yes, the UI is fantastic in how it handles this, but I was describing the general data structure. Some people had trouble grasping the mental model initially, and I found thinking of it in those terms helpful for figuring out what's going on.
Post reply on HN