@Gina the author of that piece is part of a co-op with "open" in the name but their daily driver for collaboration is a Slack channel :/ It's not like there aren't free code alternatives, both hosted and self-hostable:
@tyil what about just using a SaaSS that uses free code under the hood, instead of #Slack? Something like:
* #Gitter.im - gratis, owned and hosted by #GitLab
* #Wire - free for personal use, with extended features for paying enterprise users.
* #Zulip - gratis hosting for free code and open source projects
> everybody knows it, so nobody needs to be taught to use it.
Classic #NetworkEffect problem ;) The only way out is for some brave and forward-looking users and orgs to lead the charge.
> I'd have to make a strategy in how to nudge people towards it first, and that will take time.
Of course. The longest journey starts with a single step :)
> One benefit I personally see in Slack is that I can use it with my favourite terminal chat client, WeeChat
I wouldn't count on that lasting. Slack have taken a number of steps to force users to use their Electron monstrosity, including cutting off IRC and XMPP (classic embrace, extend, extinguish):
@clacke ooh, good question. When GitLab acquired Gitter they said:
> we will open source the whole of Gitter
It's important to hold them to that. Their repos are here:
It seems like code for all the user apps is available under free licenses, but I'm not sure if the other repos there constitute the full backend yet or not.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!