Shawn WebbOne downside to using #ZulipChat as your main method of open source project communications channel: it's not possible to sign up for a new account when connecting from #Tor.
Benedikt Ritter (he/him)Yesterday @marcphilipp proposed to the @testlens team to use @zulip for team communication. I absolutely love it! It is so much better then competitors like #slack or #msteams that went down the enshitification road long ago.
Just one example: in Zulip all topics (equivalent to Slack threads) are named and listed below the channel they belong to and topics can be marked resolved. How awesome is that?
Now Slack threads are going to feel even more painful than before...
World Basement Classic@dave A fine thing for many protocols, but for the niche that Discord / #Zulip fills it's not a dealbreaker for me.
Even the free cloud tier of #ZulipChat lets you export settings to migrate hosts, if that should ever become a requirement
Your organisation’s data will be exported in a format designed for imports into Zulip Cloud or a self-hosted installation of Zulip. You will be able to export all public data, and (optionally) private data from users who have given their permission.
Kevin Karhan 
@MxVerda @BrodieOnLinux @qdot Well, depending on what you want to develop or communicate there are various options.
Many folks went from #GitHub to @Codeberg / #Codeberg to do their #FLOSS development as it too has #IssueTrackers and means to discuss things without #loginwalled read-only access. Others like @torproject have their own @gitlab / #GitLab servers #SelfHosted.
If you want a #Chat then consider #LiberaChat if you don't demand #privacy. Otherwise @delta / #deltaChat and/or #XMPP via @monocles & @gajim may be an option.
If you do want some #LoginWalling for some reason, consider @zulip / #ZulipChat as it has a nice #threading model that can handle both asynchronous communication and high traffic without becoming unfindable or unarchiveable. Otherwise there's like @RocketChat / #RocketChat which also works great by my own experience.
Case in point: #discord just makes it more cumbersome and painful than anything. It's basically #Slack + #MicrosoftTeams, but worse…
c3hamm e.V.Derzeit probieren wir ja so alles mögliche aus, was Kommunikations-Plattformen angeht. Neuestes Fundstück:
Wer da mal unterwegs ist, kommt doch mal auffen Kaffee vorbei... Oder Mate...
Dann wollen wir morgen so ab 16:00 wieder einen VRoom "c3hamm" in EngageVR aufmachen. Nach Login einfach nach "c3hamm" suchen. Clients gibt's hier:
https://engagevr.io/engage-download-list/
+++
@zulip #zulip #zulipchat #cccregio #vr #socialvr #multiverse #metaverse
fnetX@veloren You could also have a look at #Zulipchat. It's still a chat-like thing and things could get buried, but many people consider their approach to threads superior to all other methods.
Basically, every message is assigned to a thread, and although I do not work with Zulip daily, in the communities where Zulip was used, I never had any problems with quickly finding content in chat history.
Fabrice Flore
backdropcmsWe will be having our first Community meeting of the year tomorrow. The topic will be:
Drupal 7 Migration Pipeline. An initiative to connect Drupal 7 site owners to freelancers and contractors.
Thurday, Jan 5th at 12:00pm (Pacific Time).
Check our #Zulipchat channel for more information:
https://backdrop.zulipchat.com/#narrow/stream/218635-Backdrop/topic/Weekly.20Meetings
Tim Erickson, @stpaultimNo promises, but it's not uncommon for Drupal 7 contrib module port requests to be filled within a few days, if the module is relatively simple.
It always helps to show up in our #Zulipchat instance and engage with the community.
The #BackdropCMS community uses #FOSS #Zulipchat platform for our realtime chat conversations.
Join us in Zulip anytime. Bring your questions, feedback, or just come hang out with us.
https://backdrop.zulipchat.com/#narrow/stream/218635-Backdrop