One of the common misnomers around the migration away from toxic tech stacks is that the options are either 1) services managed by a company or 2) everyone #selfhosting themselves.

There is however an often overlooked 3rd option of community-scaled infrastructure. Here a group identifies their needs, plans & deploys to meet them. Much like a community garden, that infrastructure has people skilled & dedicated to its upkeep in providing for that group, working bees & skillshare as needed.

1/n

@JulianOliver We shouldn't forget intermediates between self-hosting and megacorps. Mastodon is an obvious example: I'm not hosting this instance. (Thanks @Larvitz ). [email protected] is run by a non-profit foundation. @nextcloud comes quickly to mind. It's for-profit, but it has user-friendly principles. A similar description applies to @openstreetmap and Bandcamp.

@alison @JulianOliver @nextcloud @openstreetmap I totally agree. There are several ways to escape megacorps without actually self-hosting stuff.

There's cooperatives (like German Hostsharing e.G.), hosted services from freedom-oriented parties (Posteo, Codeberg, Proton etc.), managed solutions like masto.host, that host your own Mastodon instance for you and many more.

There's also community built services by makerspaces or local hackerspaces etc. There's all shades of grey between big-tech and self-hosting.