Julian OliverFeb 23

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

Show threadJulian OliverFeb 23

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

Show threadCRSFeb 24
@JulianOliver please use matrix bro. Mattermost isn’t that OpenSource! Most of the good things things are closed and enterprise.
Show threadJulian OliverFeb 24
@xr1st0ph Matrix/Element is great in many ways (E2EE) but memberships I've deployed for have found it too geeky, whereas alt platform averse can generally smoothly bump from Slack to MM with little to no complaints. Matrix/Element is also too sluggish for big channels of 1k+ members, even on powerful machines. Runs hot & starts to crawl in the thousands, whereas MM cruises through it. Matrix on smaller scales? Fine. I think their Olm, implementation of Double Ratchet holds them back a bit there.
Show threadJulian Oliver
@xr1st0ph MM Team Edition is FLOSS. Enterprise not so.
Feb 24 at 7:16amWeb