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
Here are some examples of this at work, in this case the Slack alternative Mattermost:
1. Our own instance in DE, used for online training
2. My friend's instance served from under her desk, on which I teach her students in CA
3. An instance in CH hosting thousands of environmental defenders that I deployed
4 An instance we deployed in IS hosting a US immigration support NGO, resistant to ICE warrants
There is no one deployment for all here, each instance meets the unique needs of the group
Crystelle, co-director of Nīkau, said an interesting thing on this, noting that across history so many human cultures have necessarily localised expertise to meet the needs of their group, building in resilience - whether carpenter, physician, mason, blacksmith, gardener, hunter etc.
She argues that today, with a dependence on complex technical infrastructures readily abused by power, communities need to incorporate system administration & infosec into the skillbase held by the membership.
Julian Oliver
AGF : poemproducer