Apps as views, not vaults.
Your data lives in a bookshelf you own; apps are just the views that read from it. A seven-part series on what the AT Protocol flips, what it doesn't, and why the “boring” architecture really does impact you a lot.
Who this is for
People who keep hearing about Bluesky and the AT Protocol and want to actually get it: web and tech folks, community builders, the platform-curious. It's an on-ramp, deliberately plain-spoken, not a deep technical dive. If you already run your own PDS and write lexicons for fun, you're not the target reader, though the honest-limits and falsifier parts (Episodes 6 and 7) might still earn your time.
The series
- Act 1 · The problem why the platforms you depend on keep costing you
- 02Identity
Your identity isn't your username
Change your handle, keep every follower. Why atproto splits who you are from what you're called.
Coming Jun 30, 2026 - 03Data
Where your posts actually live
When an app shuts down, what happens to five years of your stuff? Depends who's holding it.
Coming Jul 7, 2026 - Act 2 · The shift how atproto rewires the relationship04Interop
Apps that don't need permission
A new app can already know your network: no partnership deals, no API keys, no “log in with X” tax.
Coming Jul 14, 2026 - 05Control
You don't have to like the algorithm
When a feed decides your reach, you don't get a vote. There's an architecture where you do.
Coming Jul 28, 2026 - Act 3 · The honest case the limits, and why it's still the bet06Tradeoffs
What atproto can't do (yet)
The gaps the hype skips. Plus: your whole identity can run on a Raspberry Pi, or hosted free.
Coming Aug 4, 2026 - 07Vision
Bigger than social media
I ran Doom over the AT Protocol at five frames per second. Nobody needs that, but it proved what the protocol really is.
Coming Aug 11, 2026
Two things you should know about me
First: I'm building two products on atproto, Sifa (a professional network) and Barazo (a forum platform). I have direct skin in the game.
Second: I've been working on the internet for 25+ years, across open source communities, SaaS platforms, and social tools. After watching that many open protocols get swallowed by platforms, I think this one has a real shot. So no, this isn't a neutral take (claiming I'm neutral while building two products on it would be a bit much).
Per Taleb: writers without skin in the game produce theory; writers with skin in the game produce signal. If you'd rather have a neutral overview, there are good ones out there. This one comes with a point of view, and now you know where it's pointing.
Part 7 (the final episode) lists the concrete conditions by 2028 that would prove me wrong.
Hi, I'm Guido
I've spent 25+ years building on the internet, across open source communities, SaaS platforms, and social tools. These days I'm building two products on the AT Protocol, Sifa and Barazo, and writing about why the architecture matters. I write the way I'd explain something to a friend over coffee.
More about me- “atproto” is short for the AT Protocol. The ecosystem of apps built on it is the Atmosphere; Bluesky is one app in it, not the protocol itself.
- It's a young protocol and the facts move fast. I've dated the claims that might shift, and I'll keep the published parts current where I can.
- Each episode stands on its own. Start anywhere, but they're written to be read in order.