Defense (of the internet) (from billionaires) in depth
Picks and Shovels is a new, standalone technothriller starring Marty Hench, my two-fisted, hard-fighting, tech-scam-busting forensic accountant. You can pre-order it on my latest Kickstarter, which features a brilliant audiobook read by Wil Wheaton.
The only way to truly billionaire-proof the internet is to a) abolish billionaires and b) abolish the system that allows people to become billionaires. Short of that, any levees we build will need constant tending, reinforcement, and re-evaluation.
That's normal. No security measure (including billionaire-proofing the internet) is a "set and forget" affair. Any time you want something and someone else wants the opposite, you are stuck in an endless game of attack and defense. The measures that block your adversary today will only work until your adversary changes tactics to circumvent your defenses.
For example, mining all the links on the internet to find non-spam sites worked brilliantly for Google, because until Pagerank, there were zero reasons for spammers to get links to point to their sites. Once Google became the dominant way of finding things on the internet, spammers invented the linkfarm. This principle can be summed up as "Show me a ten-foot wall and I'll show you an eleven-foot ladder."
Security designers address this with something called "defense in depth": that's a series of overlapping defenses that are meant to correct for one another's weaknesses. Your bank might use a password, a 2FA code, and – for extremely high-stakes transactions – a series of biographical questions posed by a human customer service over a telephone line.
I've written extensively about defending a new, good internet from billionaire enshittifiers. For example, in this post, I described how Bluesky could be made enshittification-resistant with the use of "Ulysses Pacts" – self-imposed, binding restrictions on enshittification:
A classic example of a Ulysses Pact is "throwing away the Oreos when you go on a diet." Now, it doesn't take a lot of work to devise a countermeasure your future, Oreo-craving self can take to defeat this measure: just drive to the grocery store and buy more Oreos. This even works at 2AM, provided you live within driving distance of an all-night grocer.
That doesn't mean you shouldn't throw away those Oreos. Depending on how strong your Oreo craving is, even a little friction can help you resist the temptation to ruin your diet. We often do bad things because of momentary impulses that fade quickly, and simply airgapping the connection between thought and deed works surprisingly well in many instances.
This is why places with fewer guns have fewer suicides of all kinds: there are plenty of ways to kill yourself, but none are quite so quick and reliable as a gun. People in the grips of a suicidal impulse who don't have guns have more chances to let the impulse pass (this is also why gun control leads to fewer all-cause homicides). So just because a measure is imperfect, that doesn't make it worthless.
If you're trying to give up drinking, you throw away all your booze, but you also go to meetings, and you get a sponsor who can help you out with a 2AM phone call. You might even put a breathalyzer on your car's ignition system. None of these are impossible to defeat (you can get an Uber to the liquor store, after all), but they all create friction between the thing you want, and the thing your adversary (your addiction) is trying to get. They strengthen the hand of you as defender of the sober status quo, against the attacker who wants you to relapse.
Critically, all these defensive measures also buy you space and time that you can use to organize and deploy more defenses. Maybe the long Uber ride to the liquor store gives you enough time to think about your actions so you call your sponsor from the parking lot. Defense is useful even when it only slows your adversary, rather than stopping your adversary in their tracks.
Scaling up from personal defense to societal-scale security considerations, it's useful to think of this as a battle with four fronts: code (what is technically im/possible?), law (what is il/legal?), norms (what is socially un/acceptable?) and markets (what is un/profitable?). This framework was first raised a quarter-century ago, in Larry Lessig's Code and Other Laws of Cyberspace:
Lessig laid out these four forces as four angles of attack that challengers to the status quo should plan their strategy around. If you want to liberalize copyright, you can try norms (the "Free Mickey" campaign), laws (the Eldred v. Ashcroft Supreme Court case), code (machine-readable Creative Commons licenses) and markets (open access/free software businesses). Each one of these helps the other – for example, if lots of people believe in copyright reform (norms), more of them will back a Humble Bundle for open access materials (markets), and more lawmakers will be interested in changing copyright statutes (law), and more hackers will see reason to do cool things with CC licenses, like search engines (code).
But the four forces aren't just for attackers seeking to disrupt the status quo – they're just as important for defenders looking to create and sustain a new status quo. Figuring out how to "lock a system open" is very different from figuring out how to "force a system open." But they're both campaigns waged with code, law, norms and markets.
We're living through a key moment in enshittification history. Millions of people have become dissatisfied with legacy social media companies run by despicable, fascism-friendly billionaires like Elon Musk and Mark Zuckerberg and are ready to leave, despite the costs (losing contact with friends who stay behind). While many of them are moving to group chats and private Discord servers,tens of millions have moved to new social media platforms that advertise (though they don't necessarily deliver) decentralization: Mastodon (and the fediverse) and Bluesky (and the atmosphere).
Decentralization is itself a defensive countermeasure (code). When a service has diffuse power, it's harder for any one person to take it over. Federation adds another defensive layer, because users who don't like the way one server is run can move to another server, with varying degrees of data- and identity-portability. That makes it harder for server owners to squeeze users to make money (markets), and gives them an out if server owners try it anyway.
Federation with decentralization is my favorite anti-enshittification defense. It's powerful as hell. It's the main reason I endorse Free Our Feeds, an effort to (among other things) build more Bluesky servers to decrease the centralization and give users dissatisfied with Bluesky management an alternative:
That said, decentralization and federation are not perfect, set-and-forget defenses. Take email – the oldest, most successful federated system of them all. Email is nominally decentralized, but most email traffic goes through a handful of extremely large servers run by a cartel of companies (Google, Apple, Microsoft, and a few ISPs). These companies collude (or, more charitably, coordinate) to block email from non-cartel companies, in the name of fighting spam. This makes running your own mail server so hard that it is nearly impossible (that is, if you care about people actually receiving the email you send them):
https://pluralistic.net/2021/10/10/dead-letters/
What's interesting about enshittified email is that it didn't start with corporate takeover: it started with volunteer-maintained blocklists of untrustworthy servers that most email operators subscribed to, defederating from any server that appeared on the list. These blocklists of bad servers were opaque (often, their maintainers would operate anonymously, citing the threat of retaliation from criminal scammers whose servers appeared on the list). They had little or no appeal process, and few or no objective criteria for inclusion (you could be blocklisted for how your email server was configured, even if no one was using it to send spam). All of this set up the conditions to favor large email servers, and also had the effect of immunizing these large servers from appearing on blocklists. I mean, once three quarters of the internet is on Gmail, no one is going to block email from Gmail, even if a ton of spam is sent using its servers.
The lesson of email doesn't mean email is bad, nor does it mean decentralization and federation are useless. It doesn't even mean that blocklists of bad servers are evil. It just means that federation and decentralization are imperfect and insufficient defenses against enshittification, and that blocklists are useful, but very dangerous. It means that we should strive to keep our systems federated and decentralized, and watch our blocklists very carefully, and not rely on any of this as the only defense against enshittification.
Likewise, both Mastodon and Bluesky are built on free/open code and standards. That means that anyone can fork them, fix them or mod them. What's more, the licenses involved are irrevocable, making them very effective Ulysses Pacts. No one – not a CEO, not a VC investor, not a court or a blackmailer – can order someone to make their GPL code proprietary. The license is perpetual and irrevocable, and that's that.
Free/open licenses are excellent Ulysses Pacts and great code-related defenses against enshittification, but they, too, are imperfect and insufficient. Google, Facebook, Amazon, Apple and Microsoft have all figured out how to enshittify services that are built on free/open code:
And then there are all the companies that use free/open code and defeat the freedom and openness by simply violating the license, on the grounds that a decentralized, federated development community can't figure out who has standing to sue, and also can't afford to pay for the lawyers to do so:
That's not to say that code-based antienshittification measures are pointless – only to say that they need other measures to backstop them, as defense in depth. Let's talk about law, then. Both Mastodon and Bluesky are governed by legal entities that are, nominally, organized by charters that oblige them to eschew enshittification and be responsive to their users (Bluesky is a B-corp, Mastodon's code is overseen by a US nonprofit).
These structures are very important. I've been a volunteer board member for several co-ops and nonprofits (I was even once a volunteer for a nonprofit co-op!) and I'm familiar with the role that good governance can play in defending a project from internal and external pressures to betray its mission. That means I'm also familiar with the limits of these governance measures.
Take nonprofits: nominally, nonprofits are legally bound to serve their charitable purpose, and technically, stakeholders have legal recourse if they stray from this. But you don't have to look far to find nonprofits that have violated their charter and gotten away with it. Take the Nature Conservancy, which has become a key player in the market for fake "carbon offsets" that are used to justify everything from fossil fuel extraction to SUV manufacture:
Or think of ISOC, who get tens of millions of dollars in free money every year from their stewardship of the .ORG registry, but who decided to hand over control of the nonprofits' TLD of choice to a shadowy cabal of hedge-fund billionaires:
But REI is a paragon of social virtue compared to its Canadian equivalent, Mountain Equipment Coop, whose board was taken over by corrupt assholes who then sold the whole thing to a US private equity fund and change the name to "MEC":
B-corps are far from perfect, too: while they are nominally required to serve a positive social purpose, in practice, they can violate that purpose with impunity, whether that through greenwashing:
None of this is to claim that B-corps, co-ops, and nonprofits are useless. Maybe we should just give up on organization altogether and have some kind of adhocracy? If you're thinking this will help, then you need to read Jo Freeman's "The Tyranny of Structurelessness" and learn how a "leaderless" group is actually led by its least scrupulous, most Machiavellian schemers:
https://www.jofreeman.com/joreen/tyranny.htm
At this point, you might be mentally designing a new corporate structure, one that's designed to correct for both the tyranny of structurelessness and the brittleness of co-ops, nonprofits and B-corps. Please don't do this. Rolling your own corporate structure is like rolling your own cryptography or your own free software license. It always ends in tears:
I like co-ops, nonprofits and B-corps. They're powerful – but insufficient – weapons against enshittification. They need to be backstopped by other measures, like norms. Normative measures are very powerful! Of course, mass revolts of angry users don't always keep companies from enshittifying:
And of course, these defensive measures reinforce one another. The public outcry against the .ORG selloff (norms) led to California's Attorney General stepping in (law), and after that, we more-or-less romped to victory:
Markets are the final antienshittificatory force. If a social network is designed to be surveillance-resistant, it will be (very) hard to implement behavioral surveillance advertising. If a network is designed to support a many clients, it will be easy to implement an ad-blocker. Both factors make advertising-based businesses very unattractive to individual server operators, spammers, and VCs who back companies that operate elements of a federated server.
Same goes for systems that allow users to control the recommendations and other algorithmic aspects of their feeds (including switching these off altogether). The fact that Tiktok's users overwhelmingly use an algorithmic feed that they have no way to control or even understand is an anti-Ulysses Pact, an irresistible temptation for Tiktok to enshittify itself:
By contrast, it's much harder to pull those shenanigans with services that technologically devolve control over recommendations (code), making it less profitable to even try to attempt this (markets). And of course, if users refuse to tolerate this kind of thing (norms) and can hop to other servers (code), then any system that pulls that nonsense will lose lots of users and go broke (markets).
This defense-in-depth approach to decentralized social media pushes us to analyze both Mastodon and Bluesky through a tactical lens – to identify the weak parts in the defenses of each and shore them up.
Take Free Our Feeds and its attempt to stand up more Bluesky servers. This addresses one of the serious technical deficiencies in Bluesky (the lack of federation), and if lots of Bluesky users try it out, it will normalize the idea that Bluesky is a constellation of independently managed servers (norms). It also creates Bluesky alternatives with radically different commercial imperatives (markets), because the main Bluesky server is backed by venture capitalists, who are notorious for their enshittifying impulses.
But security isn't static – a tactic that works today won't work tomorrow if your adversary can figure out a way around it. Bluesky is a B-corp with an excellent board with some names I have profound trust for, but B-corps can abandon their public benefit purpose, and boards can be fired (and also even people you trust can talk themselves into doing stupid and wicked things, see .ORG).
If millions of Bluesky users flock to a rival service, one run by a nonprofit (markets), Bluesky's investors might be tempted to sever the link between Bluesky and that new server (code). That's what Facebook and Apple did to XMPP, an interoperable, federated messaging system that used to connect Apple users, Facebook users, and users of many other servers. They did this for commercial reasons (markets), to trap and lock in their users (code), and they got away with it because not enough users were outraged by this (norms) that they could get away with it.
When Bluesky's VCs fire the CEO, kick people like Mike Masnick off its board, and then defederate from Free Our Feeds' server, how do we make that more like Sonos or Unity (where the corporation capitulated to its users), and not like Reddit (where the user revolt was crushed)?
With social media, it's a numbers game. Social media grows by network effects: the more users there are in a system, the more valuable it is. It's not merely imperative to create alternative Bluesky servers, it's imperative to make them populous enough that cutting them off from the first Bluesky server will inflict more pain on the company than it inflicts on those other users. That's not a guarantee that Bluesky's future, enshittification-bent management won't go ahead and do it anyway, but it does increase the chances that if they press on, their users will take the hit to defect to free/open servers.
Bluesky has other problems besides its centralization, of course. The reason Bluesky is so centralized is that it's really expensive to run an alternative Bluesky server that provides a home for users who have left the main server (a "relay" in Bluesky-ese). Partly this is down to tooling: because no one has done it, Free Our Feeds will have to invent a lot of stuff to get that server up and running, but people who come later will benefit from whatever Free Our Feeds develops along the way.
But mostly, this isn't a tooling problem – it's an architecture problem. The way that Bluesky is structured demands a lot more of relays than Mastodon demands of "instances" (a loose Fediverse analog to relays):
This is a code problem, and it's a hard one, but it's not insurmountable. The history of networked tools is the history of developers figuring out how to break apart large, monolithic, expensive services in cheaper, smaller, easier to develop. In other words, our defense in depth of Bluesky militates for more than one project – not just a "Free Our Feeds" but also a software development project to make it easier for anyone to free those feeds.
Which raises some important questions, the biggest being "Why bother?" After all, there's already a perfectly good Fediverse that could sure use the money and effort that Free Our Feeds is proposing to put into Bluesky. My main answer here is that the point of disenshittification is an enshittification-free internet, not a better Mastodon:
We want to set Bluesky users free because the problem with Bluesky isn't its users, it's the fact that there's no fire-exits those users can avail themselves of if Bluesky's VCs set it on fire:
But there's another good reason to do this, one that involves people who have no interest in using Bluesky: even if you don't want to use a better Bluesky, you likely have very good reasons to reach Bluesky users. Maybe you want them to help you organize against enshittification! Or maybe you just want to operate a real-world venue where people can gather and have a great time and support performers, and right now you're stuck advertising on Facebook and Instagram, and you don't want to end up being forced to use an enshittified, fire-exit-free Bluesky in the future:
Of course, there's plenty of reasons to want to make Mastodon better. Many of Mastodon's features are absurdly primitive – the lack of threading support and quote-boosting sucks, and the supposedly opt-in system-wide search doesn't work, even if you opt in. Masto could sure use some of the money that Free Our Feeds is asking for to spruce up Bluesky.
This is true, but also irrelevant. Mastodon is stuck at around a million active users, while Bluesky has twenty times that amount. Crowdfunding a couple dollars per user to pursue software development is a reasonable goal, but raising twenty times that much is a lot harder:
https://mastodon-analytics.com/
The money being raised for Free Our Feeds isn't money that had been earmarked for Mastodon development, nor will abandoning Free Our Feeds redirect those funds to Mastodon development.
Which isn't to say that we shouldn't chip in to fund Mastodon development. I donated to the Kickstarter for Pixelfed, a Fediverse Insta replacement that has Meta so scared that they'll suspend your account if you even mention it:
Adding Insta-like features to Mastodon is great. Fixing search, quoting, and threading would be great, too. We probably need some kind of governance efforts to keep volunteer-run, good faith defederation blocklists from exhibiting the same dynamics that email went through during the spam wars. There's some Bluesky features I'd love to see on Mastodon, like composable moderation and user-controlled, user-tunable recommendations. We also probably need some kind of adversarial press that closely monitors the governance structure for the Mastodon codebase and reports on process in standardization (I cannot overstate how much fuckery can take place within standards bodies, under cover of a nigh-impermeable shield of boringness).
Breaking Bluesky open is a priority. Keeping Mastodon open is a priority. But neither of these are goals unto themselves. The point is to set people free, not set technology free. Willie Sutton robbed banks because "that's where the money is." Right now, I'm interested in anti-enshittification measures for Bluesky because "that's where the people are."
Check out my Kickstarter to pre-order copies of my next novel, Picks and Shovels!
If you'd like an essay-formatted version of this post to read or share, here's a link to it on pluralistic.net, my surveillance-free, ad-free, tracker-free blog:
Do you want to listen to an old communist hag ad-lib a manifesto to a random Twitch follower? Did you miss the golden age of interoperable chat apps? WELL BOY HOWDY DO I GOT NEARLY AN HOUR OF CONTENT FOR YOU!
This was the big insane edit job that taught me a lesson in "holy fuck it's not sustainable to manually caption a 40 minute video." A very important category of lesson. It's not a large category, but I have suffered greatly in learning it.
I will probably upload all of my VODs at some point with minor editing, but that's a giant project, and will not involve caption work. Just mild security censorship as necessary and some timestamps. I won't upload shorts while doing that, because again, this way lies insanity.
Your Messages Are Not Private. She Found Out The Hard Way.
Forbes reports that Facebook gave Nebraska police a teenager's private messages and used those messages to prosecute her under their forced-birth laws.
Not public posts. Her DMs. Her "private" messages.
And the fact that they were able to comply at all means those messages were not private. Meta could read, analyze, or use the data in those messages at any time.
I'm not surprised Facebook is the first service used in this manner - remember that Facebook let lots of third party apps harvest massive amounts of data without consent - but this holds true about any communication you do online that is not explicitly encrypted.
It is well past time to up your privacy game on the internet.
Particularly when it comes to messaging.
E-mail
Your e-mail is decentralized, which means that it goes through any number of possible servers before reaching its destination. Your e-mail is also unencrypted, which means anyone can read it en route. The first only becomes a problem when the second is also true, so it's time to fix that.
Get a GPG key and encrypt and sign all your email. Lifehacker’s guide at https://lifehacker.com/how-to-encrypt-your-email-and-keep-your-conversations-p-1133495744 is still good; just know that Enigmail is no longer needed with Thunderbird – it can handle it all without an extension. The TL;DR: Use Mailvelope if you must use webmail, Thunderbird for desktop email. You can also register your key with a keyserver so that others can find your key there (perhaps using a tool like this little bash script I wrote). My GPG key ID is 0xDD2F731F.
- keys.openpgp.org
- keys.mailvelope.com
- keyserver.ubuntu.com
- pgp.mit.edu
Instant Messaging
When it comes to instant messaging (including text messaging), there are a couple of major players.
When you're looking for secure messaging, there's a couple of major players, two centralized and two decentralized. A centralized messaging system means that all messages end up going through a central server, and if the company or their servers is compromised, down, or blocked, the entire communication network is down. Facebook Messenger is an example of a centralized messaging service. A decentralized service will keep going, because the network is not routed through a single server, and messages can still find their way to their destination, though that means the message passes through more hands. E-mail is a good example of a decentralized service that nearly everyone's familiar with - but unlike e-mail, encryption is far more common and easier.
The two big options for centralized messaging are Telegram and Signal. Both have their benefits; Signal can also drop-in substitute for your normal texting as well. There are plenty of feature comparisons out there; take a look to see which (if not both) is better for you. I'm on both, and should be searchable fairly easily.
- HowToGeek: https://www.howtogeek.com/709053/signal-vs.-telegram-which-is-the-best-chat-app/
- Tom's Guide: https://www.tomsguide.com/news/signal-vs-telegram
- iStarSoft: https://www.istarsoft.com/signal-vs-telegram/
While centralized messaging apps can seem easier to set up, they have the problem of being, well, centralized. Luckily, there are two big instant messaging protocols that are decentralized: XMPP (also called Jabber) and Matrix. You're actually much more familiar with XMPP than you think you are - both Facebook Messenger and Google Chat/Talk were originally based on XMPP until those companies decided to make them incompatible. Also, both of these protocols do have servers with open registration, and you can self-host a server for either if you'd prefer.
Again, think of this like e-mail. You don't blink when someone gives you an email address with a different domain name than yours; the same principle applies here. In the same way as with e-mail, you need to have end-to-end encryption enabled, as messages may pass through multiple servers. However, both XMPP and Matrix support this pretty much out-of-the-box.
Matrix's strengths are in its "bridges" - allowing you to (with the occasional caveat) to connect to all your old messaging protocols in one place. There's a good guide at https://joinmatrix.org/guide/ and a quickstart using the polished Element web interface at https://frontpagelinux.com/tutorials/beginners-guide-how-to-get-started-with-element-matrix/. There's apps for every platform with various feature sets. Personally, I use SchildiChat for Android and Nheko for the desktop. Because you're using end-to-end encryption, you do not have to self-host a server, but it is doable and there are open servers to choose from, which are covered in the guides above. There is also the Beeper project that handles all the back-end stuff for you as well: https://www.beeper.com. You can find me on the Matrix network at @[email protected] .
XMPP feels more like what you might think of as a "chat app" in a lot of ways, and is significantly a lighter-weight program than Matrix for both the server and the client. As a user, the first big decision you'll have is to choose a client. There are quite a few, with different features for different platforms. I personally use Conversations (guide here: https://ravidwivedi.in/posts/xmpp-guide/ on my phone, and have used two crossplatform clients on my desktop:
- Gajim: https://gajim.org/
- Psi+: https://psi-im.org
Linux users: Gajim is also available as a Flatpak, and Psi+ is available as an AppImage, and both are in Debian's repositories as well.
I'm recommending these two because they handle OMEMO encryption for your messages automatically, and Psi+ can even handle GPG encryption as well without any problems.
The second bit is choosing a server.
Because you're using end-to-end encryption, you don't have to self-host. If you wish to self-host, there are a lot of different solutions depending on your setup. Snikket (https://snikket.org/) has put together a docker container which will handle nearly all aspects of setup, SSL registration, web interface, and the like. With a VPS and a domain name, you could have it running in minutes.
Other than that, there are plethora of servers you could register with. There's a curated list at XMPP.org: https://xmpp.org/software/clients/, and much larger list at https://list.jabber.at/. Once you've registered, it's simply a matter of sending a message to someone else - again, just like e-mail. I can be found at [email protected] .
Again, there's nothing wrong with using multiple of these methods of communication. You do not have to choose one forever and ever, and there's no reason you should only have to choose one.
The important thing - and the thing that makes any of these different from anything owned by Meta - is that you are the one in control of who gets to see your messages.
Matrix - @[email protected] ; XMPP - [email protected] . Yes, it was a bit of a pain setting it up so I could have that.
Read the full article
wrt discord alternatives, I think something like xmpp doesn't have bells and whistles, but maybe that's kinda a good thing.
I understand that discord has this big combination of computer-messaging + calls + file-sharing + etc., but I'm not convinced that any 'everything app' is really what you want?
After 2 weeks of struggling and a lot of googling, I can now be found on XMPP at [email protected] as a replacement for discord. If you want to use XMPP then you should install Dino on desktop, Conversations on Android (doing it through F-Droid is the best cause it's free, like 3 bucks through the play store), and Monal on IOS (I don't use iPhone so I can't vouch for the quality, but it's on the app store and it's apparently the best). Calls aren't set up quite yet but I'm gonna fix that when I get home for the day.
If you just want to register on a public server, I would recommend movim.eu since it seems to be one of the bigger players in XMPP messaging. I still recommend your own server but with the hell I went through these past 2 weeks I'm not gonna blame you for wanting a simple experience.
And if any of the Moots want to use my server, I guess they could dm me and I could set up an account for them, provided they give me the username and password they want.
