Last month Terry Godier published a great essay on his website about “the boring internet,” discussing how the internet that many of us grew up with, the wonderful, empowering, exciting internet that moved power to the edges of the network rather than the center, is still there. It’s just hidden beneath enshittified commercial layers put there by companies seeking to extract more and more from you. It’s a great read and here’s just a snippet:
The internet you grew up on is not gone.
Some of its commercial superstructure is, and more of it will go. The next decade is going to be strange for any company whose value proposition was: we host the place where you talk to your friends.
The platforms will keep mutating. The feeds will keep filling. The slop will keep rising. The grief is real and you are not wrong to feel it.
But the actual internet — the protocols, the federated services, the plain-text commands, the open feeds, the small servers, the personal sites, the things people built when user and developer were sometimes the same word — is still right there.
But, as Godier’s piece notes, protocols are… boring. They change slowly (for a good reason, because you need stability to build on). They tend to change by consensus, which is messy. And rather than having billion dollar companies throwing a whole massive engineering team at making everything work, in the protocol world, we rely on constant experimentation by anyone who wants to experiment.
Sometimes that produces silly things. Sometimes it produces things that only kinda work. And sometimes, it produces wonderful new things that would never have existed in a world of fully centralized services.
But, it takes time. And that can be frustrating for those of us who want to live in that better future. The important thing for people to understand, though, is that while the amazing new breakthroughs in the protocol world may not get giant headlines in the NY Times or flashy stories about trillion dollar IPOs, they are building real things for real people, in which the people are the most important part, rather than the bankers or the billionaire execs looking to get richer.
So I was excited recently to take part as a juror for the Open Social Awards, put on by New_Public and Public Spaces, reviewing a wide range of projects looking to build on open social protocols (mostly ATproto and ActivityPub). The energy among developers right now for what they can do on open social systems is real, and it’s building fast. Tim Trautmann recently wrote about this, saying “the nerds are building a new internet.” As he wrote:
The open web of the nineties didn’t win because the tools were better. It won because a critical mass of people decided that the alternative, a handful of AOL-style walled gardens choosing what everyone saw, was not the future they wanted. Then they built their way out of it. Slowly, unglamorously, in rooms that looked a lot like this one.
Whether atproto ends up being the thing, or a stepping stone to the thing, I don’t know. Nobody in the room claimed to know. But the work is real, the apps are shipping, and the people building them are taking it seriously without taking themselves seriously. That combination is rare, and historically, it’s the one that wins.
You can see that kind of excitement as well in this recent video of a bunch of developers doing an ATproto hackathon, where you see people realizing in real time how powerful ATproto is in allowing you to build a better internet:
It’s so easy these days to get down on the state of the larger internet, increasingly controlled by bigger and bigger companies trying to extract more and more from you. But if you look beneath all of that, genuinely interesting, important things are being built, some of which was celebrated at the Open Social Awards last week.
The grand prize winner was the Newsmast Foundation, which has been helping mission-driven organizations build their own social spaces online, using ActivityPub. They’ve been building some amazing community apps for news organizations, non-profits, and more. Enabling those organizations to have their own social spaces, but built on top of an open protocol.
The two “Excellence Award” winners were equally strong — there was a real argument that either of them could have taken the grand prize. First there’s Blacksky Algorithms, which has built out an entirely separate and differentiated ATproto experience, where thousands of users can have a social media experience interoperable with Bluesky and others on the network, but without ever touching Bluesky hardware or software. The company keeps doing really fascinating things as well, including its use of pol.is for community decision-making, and offering up its ability to build entirely independent ATproto powered communities to others via Acorn.
And there’s one of my personal favorites, Sill, which is a wonderful cross-protocol newsreader app. You login with your Atmosphere (ATproto) handle and/or your ActivityPub handle, and it will find the news that is being discussed among your followers and format it in a nice digest format. I use it as a daily review of what’s happening in the world that’s interesting to me.
And then all of the “honorable mentions” were doing interesting things as well, figuring out ways to make open social more useful: Bounce (a tool for migrating between AcitivtyPub and ATproto while bringing your community with you, from the team who also does BridgyFed, a tool for communicating across protocols). Dandelion, an events platform built on ATproto. Streamplace, which does video streaming on ATproto. Leaflet, which has become one of the go to places for long form blogging within the ATproto world, and Bonfire Networks, which is also working on helping communities build their own communities online.
There were many other entries as well, and the energy developers are bringing to open social projects right now is genuinely contagious. People are learning that they can just build stuff, and specifically the kind of stuff that you had to rely on the goodwill (or perhaps commercial agreements) of a large company to build.
Every day there are more creative new ideas showing up. The one thing I’m looking forward to most is when we start to break out of the “rebuilding this centralized service on open protocols” and finally get to the point where we get entirely new things that are only possible because of open protocols. This is how these things have always worked. A new medium first gets used to rebuild familiar things — almost as a way of learning how the underlying system operates. Then come the breakthroughs that are only possible because of that new medium. If I had one complaint about the entries this year, it’s that too many of them felt like rebuilding the old things, just on a protocol.
We’re already starting to see small examples, though, of what it looks like when we go to the next stage, and it’s not just “this service, but without centralized control” to “we can function entirely differently without centralized control.” That’s just starting to happen, but I expect we’ll see many more examples in the near future.
In the meantime, congrats to the winners (and all the entrants) of the first ever Open Social Awards.
Disclosure: I’m on the board of Bluesky, which was inspired by my “Protocols, Not Platforms” paper. But this post isn’t about Bluesky the app. It’s about the underlying protocol and what it enables for anyone who wants to build technology (even competitive to Bluesky) that actually respects users.
Last month, I helped release the Resonant Computing Manifesto, which laid out a vision for technology that empowers users rather than extracting from them. The response was gratifying—people are genuinely hungry for an alternative to the current enshittification trajectory of tech. But the most common piece of feedback we got was some version of: “Okay, this sounds great, but how do I actually build this?”
It’s a fair question. Manifestos are cheap if they don’t connect to reality.
So here’s my answer, at least for anything involving social identity: build on the ATProtocol. It’s the only available system today that actually delivers on the resonant computing principles, and it’s ready to use right now.
The Resonant Computing Manifesto laid out five principles for building technology that works for people:
Private: In the era of AI, whoever controls the context holds the power. While data often involves multiple stakeholders, people must serve as primary stewards of their own context, determining how it’s used.
Dedicated: Software should work exclusively for you, ensuring contextual integrity where data use aligns with your expectations. You must be able to trust there are no hidden agendas or conflicting interests.
Plural: No single entity should control the digital spaces we inhabit. Healthy ecosystems require distributed power, interoperability, and meaningful choice for participants.
Adaptable: Software should be open-ended, able to meet the specific, context-dependent needs of each person who uses it.
Prosocial: Technology should enable connection and coordination, helping us become better neighbors, collaborators, and stewards of shared spaces, both online and off.
If you’re building anything that involves users having identities, connecting with other users, or creating content that belongs to them—which describes basically every interesting app—you need infrastructure that makes these principles achievable rather than aspirational.
ATproto delivers all five.
Private and Dedicated come down to who controls your data. In the current paradigm, you’re rows in somebody else’s database, and they can do whatever they want with those rows. Dan Abramov, in his excellent explainer on open social systems, describes the problem perfectly:
The web Alice created—who she follows, what she likes, what she has posted—is trapped in a box that’s owned by somebody else. To leave is to leave it behind.
On an individual level, it might not be a huge deal.
Alice can rebuild her social presence connection by connection somewhere else. Eventually she might even have the same reach as on the previous platform.
However, collectively, the net effect is that social platforms—at first, gradually, and then suddenly—turn their backs on their users. If you can’t leave without losing something important, the platform has no incentives to respect you as a user.
With ATproto, your data lives in your own “personal repository” (the PDS)—think of it as your own storage container on the social web. You can host it with a free service (like Bluesky), a paid provider, or on your own server. If your current host turns evil or just annoys you, you pack up and move without losing your identity, your connections, or any of your content. The protocol handles the redirection automatically.
This isn’t theoretical. People are doing it right now. The infrastructure exists. You can literally move your entire social presence from one host to another and nobody who follows you needs to update anything (or even realize that you’ve moved).
You don’t need to figure out ways to extract data from an unwilling billionaire’s silo. It’s already yours.
And that’s beneficial for developers as well. If you’re trying to build a system, setting up the identity and social connections creates all sorts of challenges (and dangerous temptations) regarding how you deal with other people’s data, and what games you might play to try to juice the numbers. But with ATproto, the incentives are aligned. Users control their own data, their own connections, and you can just provide a useful service on top of that.
Plural is baked into the architecture. Because your identity isn’t tied to any single app or platform, you can use multiple apps that all read from and write to your personal repository. Abramov explains this clearly in that same post:
Each open social app is like a CMS (content management system) for a subset of data that lives in its users’ repositories. In that sense, your personal repository serves a role akin to a Google account, a Dropbox folder, or a Git repository, with data from your different open social apps grouped under different “subfolders”.
When you make a post on Bluesky, Bluesky puts that post into your repo:
When you star a project on Tangled, Tangled puts that star into your repo:
When you create a publication on Leaflet, Leaflet puts it into your repo:
You get the idea.
Over time, your repo grows to be a collection of data from different open social apps. This data is open by default—if you wanted to look at my Bluesky posts, or Tangled stars, or Leaflet publications, you wouldn’t need to hit these applications’ APIs. You could just hit my personal repository and enumerate all of its records.
This is the opposite of how closed platforms work. You’re not locked into any single company’s vision of what social software should be. Different apps can disagree about what a “post” is—different products, different vibes—and that’s a feature, not a bug. Your identity travels with you across all of them.
Indeed, we’re seeing some really cool stuff around this lately, such as with the new standard.site lexicon for long form publishing on ATproto. It’s been adopted by Leaflet, Pckt, and Offprint, with others likely to come on board as well.
Tynan Purdy, writing via the brand new Offprint (itself an ATproto app), captures the mindset shift that I think more developers need to internalize:
I have no more patience for platforms. I’m done.
Products come and go. This is a truism of the internet. Do not expect any particular service to exist forever, or you will be burned. It can be a depressing thought. So much of our lives are lived online. Communities and culture are created online. The play is performed on stages we call “social media”. But then they go away.
We make our homes on these platforms. Set up shop. Scale a business. Connect with our friends. Build a following. Then something changes. A change in corporate strategy. An IPO. A private equity takeover. A merger with AOL. And it’s never the same after that. All that work, all that culture, now painted in a different light. Sometimes locked away entirely.
His solution? Never build on closed platforms again:
I write to you now on a new kind of place on the internet. This place is mine. Or rather, what I create here is mine. This product (a rather fine one by @btrs.coif I say so myself), belongs to @offprint.app. They might go away. Someday they will. But this, my words, my creation. The human act of creating culture. This is mine. It lives in my personal folder. I keep my personal folder at @selfhosted.social. They will go away someday too, and that’s okay. I’ll move my folder somewhere else. You’ll still be able to read this. Offprint is just an app for reading a certain kind of post I publish to the ATmosphere. When Offprint inevitably dies, hopefully a long time from now, this post will still just be a file in my personal folder. And when that day comes, perhaps even before, there will be other ways to read this file from my personal folder. You can even do so right now.
That’s not idealism. That’s how ATproto actually works today.
Purdy mentions above his “personal folder” and in another post Abramov digs deeper into what that means:
This might sound very hypothetical, but it’s not. What I’ve described so far is the premise behind the AT protocol. It works in production at scale. Bluesky, Leaflet, Tangled, Semble, and Wisp are some of the new open social apps built this way.
It doesn’t feel different to use those apps. But by lifting user data out of the apps, we force the same separation as we’ve had in personal computing: apps don’t trap what you make with them. Someone can always make a new app for old data:
Like before, app developers evolve their file formats. However, they can’t gatekeep who reads and writes files in those formats. Which apps to use is up to you.
Together, everyone’s folders form something like a distributed social filesystem:
This is a fundamentally different relationship between users and services. And it breaks the economic logic that makes platforms turn against their users.
It’s an enshittification killswitch.
Cory Doctorow’s framing of enshittification notes that the demands (often from investors) for companies to extract more and more pushes them to enshittify. Once they have you in their silo, they can begin to turn the screws on you. They know that it’s costly for you to leave. You lose your contacts. Your content. Your community. The switching costs are the leverage.
ATproto breaks that leverage.
Because you control your data, your identity, and your connections, whichever services you’re using have strong incentives to never enshittify. Turn the screws and users just… leave. Click a button, move to a different service, take everything with them. The threat that makes enshittification profitable—”where else are you gonna go?”—has no teeth when the answer is “literally anywhere, and I’m taking my stuff.”
Paul Frazee, Bluesky’s CTO, talks about how this works in a post he recently did on the concept of “Atmospheric Computing.”
Connected clouds solve a lot of problems. You still have the always-on convenience, but you can also store your own data and run your own programs. It’s personal computing, for the cloud.
The main benefit is interoperation.
You signed up to Bluesky. You can just use that account on Leaflet. Both of them are on the Atmosphere.
If Leaflet decides to show Bluesky posts, they just can. If Leaflet decides to create Bluesky posts, they just need to use the right schema. The two apps don’t need to talk to directly to do it. They both just talk to the users’ account hosts.
Cooperative computing is possible.
The most popular algorithm on Bluesky is For You. It’s run by Spacecowboy on *squints* his gaming PC.
He ingests the firehose of public posts and likes and follows. Then the Bluesky app asks his server for a list of post URLs to render. The shared dataset means we can do deeply cooperative computing. An entirely third party service presents itself as first-party to Bluesky.
Because Tangled is Atmospheric, your self-hosted instance would see all of the same users and user activity as the first instance would.
The garden is unwalled.
SelfHosted.social is an account hosting service. The self-hosted users show up like any other user. If I had to guess, most of them started on Bluesky hosts, and then used something like PDS Moover to migrate.
It’s an open network.
In the Atmosphere, it does make sense to run a personal cloud, because your personal cloud can interoperate with other people’s personal clouds. It can also interoperate with BobbyCorp’s Big Bob Cloud, and the corner pie shop’s Pie Cloud, and on it goes.
There’s no silo to lock you in, and thus trying to turn the screws on users should backfire. Instead, services built on ATproto have “resonant” incentives, to keep you happy, to keep you feeling good about using the service, because it enables a plurality of other services as well.
In many ways it’s a rethinking of the entire web itself and how it can and should work. The web was supposed to be interoperable and buildable, but all our data and identity pieces got locked away in silos.
ATproto breaks all that down, and just lets people build. And connect. And share.
Adaptable is where the developer ecosystem comes in. Because the protocol is open and the data formats are extensible, anyone can build whatever they want. We’re already seeing this explosion right now: Bluesky for microblogging, Leaflet for long-form publishing, Tangled for code collaboration, Offprint for newsletters, Roomy for community discussions, Skylight for shortform video, Semble for organizing research, teal.fm for music scrobbling and dozens more. Some of these are mere “copycats” of existing services, but we’re already starting to see some others that are branching out beyond what was even possible before.
The key: these apps don’t just coexist—they can actively benefit from each other’s data. Abramov again:
Since the data from different apps “lives together”, there’s a much lower barrier for open social apps to piggyback on each other’s data. In a way, it starts to feel like a connected multiverse of apps, with data from one app “bleeding into” other apps.
When I signed up for Tangled, I chose to use my existing @danabra.mov handle. That makes sense since identity can be shared between open social apps. What’s more interesting is that Tangled prefilled my avatar based on my Bluesky profile. It didn’t need to hit the Bluesky API to do that; it just read the Bluesky profile record in my repository. Every app can choose to piggyback on data from other apps.
An everything app tries to do everything the way they tell you to do it. An everything protocol-based ecosystem lets everything get done. How you want. Now how some billionaire wants.
It’s becoming part of the motto of the Atmosphere: we can just do things. Anyone can. For years I’ve written about how much learned helplessness people have regarding social systems—thinking their only option is to beg billionaires or the government to fix things. But there’s a third way: just build. And build together. That’s what ATproto enables.
And it’s doable today. Yes, there are reasonable concerns about the hype machine around AI and vibe coding—but the flip side is that in the last couple of months, I, a non-professional coder, have built myself three separate things using ATproto. Including a Google Reader-style app that mixes RSS and ATproto together. That’s what “adaptable” actually means: tools malleable enough that regular people with little to no experience can shape them to their needs. The vibe coding revolution will enable even more people to just build what they want, and they can use ATproto as a foundational layer of that.
This used to be close to impossible. The big centralized platforms learned to lock everything down—sometimes suing those who sought to build better tools. ATproto doesn’t have that problem. We don’t need permission. We can just do things. Today. And with new AI-powered tools, it’s easier than ever for anyone to do so.
Prosocial is where this all comes together. Not “social” in the Zuckerbergian sense of harvesting your social graph to sell ads, but social in the human sense: enabling connection and coordination between people, without a controlling body in the middle looking to exploit those connections. The identity layer handles the hard problems—authentication, verification, portability—so developers (or, really, anyone—see the adaptable section) can focus on building things that actually help people connect.
Remember why people flocked to social media in the early years? They got genuine value out of it. Connecting with friends and family, new and old. But once the centralized systems had you trapped, those social tools became extraction tools.
The open social architecture of the Atmosphere means that trap can’t close. We can engage in prosocial activities without fear of bait-and-switch—without worrying that the useful feature we love is just bait to drag our data and connections into someone’s locked pen.
The protocol itself is politically neutral infrastructure, like email or the web. The point isn’t any particular app—it’s that we finally have a foundation for building social tools that don’t require users to surrender control of their digital lives.
If you’re building an app that needs user identity, or user-generated content, or any kind of social graph, you don’t have to build all that infrastructure yourself. You don’t have to trap your users’ data in your own database (and worry about the associated risks). You don’t have to make them create yet another account and remember yet another password. You can just plug into ATproto’s identity layer and get all of the resonant computing principles essentially for free.
Your users keep control of their identity. Their data stays under their control, but available to the wider ecosystem. Your app becomes part of that larger ecosystem rather than just another walled garden, meaning you’ve also solved part of the cold start problem. Over 40 million people already have an account that works on whatever it is that you’ve built. And if your app dies—let’s be honest, most apps die—the data and connections your users created don’t die with it.
The Resonant Computing Manifesto talked about technology that leaves people “feeling nourished, grateful, alive” rather than “depleted, manipulated, or just vaguely dirty.” That kind of technology can’t exist when the fundamental architecture treats users as resources to be extracted. But it can exist when users control their own data, when developers can build without permission, when leaving doesn’t mean losing everything.
That’s not a future we need to wait for. That’s ATproto. Today.
So when people ask “how do I actually build resonant computing?” this is a key part of the answer. Stop building on platforms. Stop begging billionaires to be better. Stop waiting for regulators to save you.
The tools are here. The infrastructure exists. We can just do things.
