@victoria I'm also reminded of all the pseudo-accreditations we'd give to websites in the earlier days of the net- little icons saying that the site is trusted by so and so, or has valid xhtml, or works with the latest netscape. All significantly less meaningful than a guarantee you aren't entering a roach motel.
@victoria this feels like the computering equivalent of building codes, like making sure that a place has exits before it's occupied
The best way to align incentives for software companies - that is, to bring "most functional, useful software" in line with "most profitable software" - is to require that most classes of software have robust data portability guarantees, both in and out, before asking for money.
Only when most software is built in such a way that users can simply, easily, and quickly move between comparable solutions will software companies be forced to optimize for utility to the user, rather than lock-in or network effects.
why cohost is problematic (long)
Okay, so let's talk about this cohost thing for a bit.
It sounds great on the surface - a small-scale, worker-owned, sustainable social media platform, run by some trusted people! Great, right?
Not so much, unfortunately. If you click through a bit, you'll find that it's run by "anti software software club llc", which claims to be a "non-profit software company". Except that's legally false (LLCs are not non-profit), and practically very unlikely to actually work out like you might think. In reality, it's an unaccountable power structure, and one that is bound to end in disaster.
They're not the *first* to do this - both YourAnonNews and npm (the JS package registry) have a very similar origin story. A small hobby project by some activist-minded people, trusted by the community, incorporated into a for-profit legal form to keep the lights on, promising to always keep serving the community. Of course, there's a reason I'm mentioning them - both of these projects turned into large unaccountable power structures that ended up doing far more harm than good, and significantly damaging a movement.
They scaled up, and whether through naivete or otherwise, the founders were unable to continue acting in the best interest of the community and broader society. Both of them became a blight on their respective communities, actively interfering with the efforts of others in that community to right the ship.
But they'd grown "too big to fail", too big and closed-down to replace or disavow. They ended up *controlling* the community rather than serving it.
A company is not a community. It is hierarchical; it has owners, employees, people with a specific role who decide how it gets run. This makes a worker-owned company a decent option when the decisions being made only affect the workers, as there's good representation.
But... that is not what's going on here! There is *no way* in which a worker-owned company can accurately represent the interests of a community of people *who do not actually work there*. Worker-owned companies are not magical fairy dust that guarantee equity and representation. You need actual community governance structures for that.
So... cohost is problematic. It is a power structure which is prone to abuse (deliberately or otherwise), not accountable to anybody, with no proper community governance model nor any real room in its incorporation form to *create* such a governance model, it is a proprietary and closed system that does not interoperate with other systems, and most worryingly of all it is a platform that becomes more valuable as it grows.
In other words: all the ingredients for a perfect storm of power abuses and harm several years down the line. Whether you personally trust the founders doesn't really change that - it's set up for failure from the very start, even assuming the best intentions.
As an activist community, we really need to do better on this - recognize such problematic power structures *before* they grow big enough to cause widespread harm, and encourage people to select governance models that *don't* suffer from these issues.
@uint8_t i'm interested in this too but i don't know of any great solutions. in practice the best i've been able to do is an old supermicro 4U that i power off when i'm not using. an alternative i've considered is to use an array of small nodes with Ceph but i don't think you'd hit 10Gb there without each node also being expensive.
@tindall I feel like this phenomenon is part of the history they're repeating too. A small new exciting thing gets boosted by people's desire to be part of a cool new thing that people they know are doing, and opposition to that makes you the outgroup.
@tindall I have seen a few people do that and imo it's immediately showing a symptom of the flat namespace and the rush of a new ingroup thing. Again not bad or worse, but immediately repetitive.
@tindall it makes me tired.. like I don't expect it to be worse or even bad, I've just been on this ride before and I don't want back on
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!