#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)
@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 @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.
@boris @jcb we're in the process of migrating from Announce / Knowledge base topics in Zulip to #Notion.
Both my company and @jcb 's self-host because it's better / cheaper than buying hosted instances. The only trick is to scale the instance as the community grows s.t. there are no random restarts of zulip's systemd service.
@jonn @jcb thanks! So you treat it as persistent? Do you have another long form writing space that is not GitHub for docs / knowledge base / handbooks / etc?
Do you selfhost?