Welcome to the Atmosphere!

life

ยท

tech

November 16th, 2026

3 minute read

I had the pleasure of stumbling upon research by Ink & Switch, which led me down the rabbit hole of local-first applications. The central idea is that files on your computer are your files. Applications let you work with those files without taking ownership of them. Online applications offer benefits like real-time collaboration, but often take your files hostage by keeping them on their servers. Depending on the application, losing your internet connection can also mean not being able to do any work. The local-first effort aims to give users control over their data while keeping the collaborative features that online applications tout. I highly recommend reading more here.

But what does this have to do with the Atmosphere? And why am I capitalizing it? The same day that I started thinking about who owns our data, I met a game developer turned creative technologist whose interests include jailbreaking iOS devices. Intrigued, I read a primer on digital communities on their blog, which helped me understand what makes Bluesky different from other social media platforms. The moment reminded me of discovering Blender โ€” and the broader applications of 3D software โ€” for the first time. Bluesky is built on ATproto. The collection of applications built on that protocol is referred to as the Atmosphere. It brings that same separation of concerns (data versus experience) into the social web.

Social media platforms have a stranglehold on our data (and, by extension, us). ATproto seeks to change that through the "open social web." To oversimplify, users control a portable repository of their public records (posts, likes, etc.), hosted on a Personal Data Server, or PDS. Applications let you interact with that data and might publish a lexicon that defines the format of the data they work with. Your identity on ATproto has a DID (Decentralized Identifier), which is linked to the data on your PDS in a cryptographically verifiable way.

The idea is that your data and identity exist independently of any one application. Applications might still run servers to offer features of their own, but if an application went belly-up tomorrow, your data would still be on your PDS, provided your PDS remained online. If you're asking, "Who owns my PDS? Does every user need to host their own server? What if the host of the PDS goes down?" then you have good instincts. I've left out a lot of technical details. For more, see the ATproto website or this overview.

Both local-first and ATproto seek to give users control over their data while keeping the features they've come to expect from modern applications. ATproto isn't a perfect solution to this problem1, and other approaches already exist2, but I think the technology is cool and the mission worthwhile. I wanted to get my feet wet.

I'm proud to say that this website is now on the Atmosphere! What does that mean? First, I created an account on Bluesky. Then I associated with the account with my domain (@suchaaverchahal.com). That means that my DID is connected to my domain, so any ATproto app will let me log in with my domain. Because I created my account through Bluesky, Bluesky hosts my PDS, which you can browse here. Using the Standard.Site lexicons, I've published a record for this website, along with metadata for all my published blog posts, to my PDS.

I've also created a project log page for my game Whirlybirding, which pulls the records straight from my PDS, not through Bluesky's application API. The page obtains image URLs through Bluesky's public API, then loads the images from its content delivery network (CDN). The original images could also be fetched directly from my PDS. It's worth noting that you could pull my public data from my PDS too, without depending on access to Bluesky's application API. That's ATproto by design โ€” it's verifiably my data, but anyone can look. There's a beauty in that.

I already have a few ideas in my head for Atmosphere-enabled experiences. If reading this piqued your curiosity, I highly encourage reading all the literature!

  1. Non-public data is complex in this implementation, but ATproto has a spaces proposal that attempts to address it.
  2. You may have heard of Mastodon, or the Fediverse more broadly.

You can get any new thoughts to your inbox by subscribing.