#matrix IM is the worst thing that happened to FOSS communication. Nerd-only software gatekeeps contributions.

@jonn I am looking at this right now for our co-op members and I currently like none of my options.

Thinking about a Discourse forum install (which is obviously not chat but fills some other roles).

For chat, a Signal group might be the best trade off (but obviously is challenging if the group gets big)

@boris #zulip!!! Zulip is perfect for coops and building in public.

@jonn I can see using it for internal operations, not sure if I can get all members onboarded and comfortable.

I’m aiming for “mass market comfort with tech” but may in fact need to adjust to “some early adopter comfort”

I appreciate the +1 on it. It’s the kind of enthusiasm I’m looking for!

@boris my company uses it, @jcb's uses it and #lean programming language too. So count as +3. If you want to learn more about my experience with #Zulip, feel free to book a 15' call.

https://savvycal.com/manpages/15

@jonn @boris I strongly recommend Zulip. It takes a little getting used to at first, but the stream and topic-based threading scales incredibly well and I can’t imagine running a distributed team without it

@jcb @jonn thank you for the feedback!

Are there any “here’s how we setup #Zulip to run our team” write ups you two have seen?

@boris @jcb the biggest revelation I had was from a friend of mine, Vlad Shcherbina who said "treat #Zulip as a realtime #bbs system like #phpbb".

If you get that, the management becomes organic.

@boris @jcb additionally, I feel like the following are the highest impact suggestions I can make:

1. Allow as many people as possible to move messages from topic to topic.
2. Encourage moving conversations that went on a tangent to their own topic (you normally know it went on a tangent whem you see it).
3. Make special slow "announcement" topics, encourage posting only really important information there.