At the Zulip open-source project, we've had a significant onslaught of AI slop in the past few months. It gets as absurd as PR descriptions with AI-generated "screenshots" of the app to "demonstrate" the changes. We've had to start warning contributors that we won't be able to review their work if they continue misusing AI, and occasionally banning repeat offenders. It's feels draining -- we want to spend our time mentoring people who'll actually learn from feedback, not interacting with contributors who are just copy-pasting LLM responses without thought.
it's really strange, I maintain a lot of OSS and I just don't see it. I've had a bit of slop, and the # of PRs I receive has 10x'ed, but the quality is generally quite good. I wonder if maybe it's because I make dev tool CLIs that are just easier for AI to work with?
Zulip's product lead here. Communities are eligible for a free Community plan if they self-host, and there are discounts and sponsorships available for Zulip Cloud as well.
Zulip | Go-to-market leader | REMOTE or San Francisco | Full-time | https://zulip.com/
At Zulip, we’re out to build the world’s best collaboration platform, and give users control over their data. Zulip is the only modern team chat app that is designed for both live and asynchronous conversations. Our product serves as the communication hub for businesses, open-source projects, educators and communities around the world.
We’re increasing our focus on go-to-market initiatives, and are looking for a go-to-market leader with hands-on B2B startup experience to take our business to the next level. This is a unique opportunity to take a well-engineered product with traction at thousands of organizations and drive the process of bringing it to a huge potential audience.
Zulip's product lead here. Yep, reading messages thread by thread is the recommended way for most folks. (There's even a keyboard shortcut for going to the next one.) The inbox view, which lists the threads where you have unread messages, is the default home view (unless your org admins changed that setting).
The combined feed is helpful for some (e.g., in lower-traffic organizations, or if you like to see messages as they come in), and was the default home view many years ago.
Zulip's product lead here. We hear from a variety of folks that they've had a good experience with onboarding to Zulip, https://zulip.com/case-studies/gut-contact/ being a good example. That said, the mental model for using Zulip is a bit different from other chat apps, and I think it helps a lot to approach onboarding with intention.
Making the experience of getting started with Zulip more smooth has been an ongoing priority for the past couple of years, and we've got more in the works. If there are particular aspects of the app that felt too technical, I'd love to get the feedback.
Hi! I like Zulip a lot and the tech team took to it easily. The main concern is silly but I think my folks will be thrown by a few UX elements. For example, uploading a file drops a bunch of markdown in the message editor.. which to them looks like an error or something weird and technical. I wish for a editing mode that showed preview instead.
I don't think it's a blocker and we can help people understand it. Its just really about how much time I want to spend with them on the phone :)
We charge businesses for our push notifications service because we need folks using our 100% open-source product to run their business to help pay the cost of developing it.
Absolutely! Reworking the onboarding experience is one of our main focus areas right now; we plan to remove the bubbles altogether, and replace them with other types of onboarding content.
Zulip | Senior Flutter Engineer | REMOTE or San Francisco | Full-time | https://zulip.com/
At Zulip, we’re out to build the world’s best collaboration platform, and we’re committed to keeping it 100% open source. Zulip is the only modern team chat app that is designed for both live and asynchronous conversations. Our product serves as the communication hub for businesses, open-source projects, educators and communities around the world.
We're building the next generation of Zulip's mobile apps in Flutter. We're looking for a senior engineer with Flutter experience to join our small core team and help define the future of team chat. Our Flutter prototype is just a few months old, so this is a greenfield opportunity to help shape the app's architecture from early on.
Our evolving AI policy is in the same spirit as ghostty's, with more detail to address specific failure modes we've experienced: https://zulip.readthedocs.io/en/latest/contributing/contribu...
reply