making more internet at @jaz.bsky.social's side has been an honor and a privilege. so many late nights hacking or plotting, situation rooms weathered, and doing some of the best work of our lives together. and a great bud. soo, so sick. jaz rules 💜

okay and as promised, the bluesky PDS is officially open for returning users to migrate their accounts back! hoping this lowers the stakes & gives folks the confidence to explore some other PDSs in the network! docs.bsky.app/blog/incomin...

i wrote about atproto and why it matters

New blogpost alert: jazco.dev/2025/09/26/i... This one is about using load balancing and bucketing in more creative ways to solve problems with database contention. Part of the work we're doing building out a new DB layer on top of FoundationDB that will be FOSS! Hope you enjoy it!

excited to share that we are following through on our earlier commitments and putting together an independent+neutral organization to house the DID PLC system, includes the directory service

Just a draft, but a very exciting draft to have www.ietf.org/archive/id/d...

@sheharper.com happy birthdayyyyyy

hi Bluesky! 🦋 i’ve been chosen as the new head of product here at Bluesky HQ! and i couldn’t be more excited to hack with this incredibly talented team on making this site better for everyone.

Adversarial ATProto PDS Migration www.da.vidbuchanan.co.uk/blog/adversa... aka how to migrate your account if your old PDS explodes, and how to prepare for it in advance

"Social media users are tired of losing their identity and data every time a platform shuts down or pivots. In the ATProto ecosystem, users own their data and identities. Bluesky is the first big example, but a new wave of decentralized social networks is just beginning."

new capabilities for atproto devs coming sooooon! take a close look, and you'll find some pretty unique stuff going on in here. one of the key questions is: how will users understand what data they're providing an app access to when they login? lexicon authors will play a very important role... 👀

appviewappviewappview - after 6 months, I'm running what is, afaik, the first full-network bluesky appview - you can use it at zeppelin.social, query it at bsky.zeppelin.social, read about it at whtwnd.com/futur.blue/3..., & help me keep it up for more than a few weeks at github.com/sponsors/fut...

OAuth updates for app devs! Over the past few weeks we've been chatting with devs and doing a pass over our SDKs and docs to address issues. This blog post summarizes the main changes we've made, some tweaks still in flight, and links to longer form writing about security and design trade-offs

tried to give some intuition for how fraught the oauth authorization code flow is, how the atproto oauth profile secures it, and lots of info for app devs engaging closely with this. a few things really jumped out at me while writing...

we've rolled out some small changes to the DID PLC directory which make it possible to register new key types as verificationMethod entries, for non-atproto use cases. (this does not impact the PLC rotation key mechanism itself; that is still limited to P-256 and K-256) have fun building on PLC!

fresh atproto proposal! this one is for the oauth, app architecture, and security folks: github.com/bluesky-soci... here we're defying the labels of traditionally "public" vs "confidential" oauth clients, and challenging assumptions about what it means to be a browser-based app. 1/8

are you a dev building an independent app on atproto and want a smoother OAuth account sign-up flow? are you a user wanting visibility and control over OAuth sessions? PDS operator wanting to add some ✨sparkle✨? this blog post is for you!

pretty damn close to a 100% top-to-bottom bluesky-free bluesky ✅ indie pds (lots) ✅ indie relay (mine + others now!) ✅ indie jetstream (mine + many more (optional)) 🌀 indie appview (AppViewLite has some issues, @futur.blue's should work, more in progress) ✅ indie client (@aviva.gay's deer.social !)

very excited about lower costs with new Sync v1.1 relay, and did a write-up on how to host one cheaply (though @bad-example.com and @futur.blue kind of got me beat on the price point)

interested in relay infrastructure and firehose protocol details? we have an update for you about our new relay implementation, and progress on rolling out Sync v1.1

oh hey guess what it's an EU-jurisdiction atproto relay. hosted in france on an OVH eco KS-1 box: 4 cores/8 threads 32GB ram 480GB redundant SSD and 300mbit unmetered connection for three million dol-- i mean, sorry, it's $18.22 in USD/mo.

first class support for intermediaries, rebroadcasting, and rehosting is lowkey goated when materially decentralizing administrative control is the vibe.

to anyone who says bluesky is not decentralized, i ask you: has anyone ever had their (and only their) social identity physically stolen and been able to recover said stolen social identity?

here's a little nugget on the structure of the merkle search tree (mst) at the heart of atproto repositories. first context: the mst is essentially a key-value store. not often pointed out: its structure is fully determined by its keys and not its values. sometimes i like to think of it as a grid:

lovely plc headquarters

banger

so much fun! / boil those beans! 🥲

Personal Data Servers (PDS) mentioned in @forbes.com — we’ve come a long way (Blacksky & Friends mentioned too)

A world without Caesars: How the atproto community is rebuilding the web to return power to the people

this time last year, we were struggling to get mainstream press to see bluesky as anything other than a "twitter alternative" very cool to now read articles that situate bluesky as just one part of the AT Protocol ecosystem, where social media isn't built by a company but rather by community

#atmosphereconf was unreal. this community is soo damn cool and knowledgeable. also a great reminder this work has roots, is just part of what will be a very long tradition. slides for my talk can be found somewhere in here! pdsls.dev/at://did:plc...

couple #atmosphereconf questions around what apps/projects we'd love to see here is a big list we have today! will try to get out something punchier soon

for any devs working on sync v1.1 induction firehose: I added verification functionality to goat, which should be pretty close to new spec and new relay. you can run it against a PDS, eg: 'goat firehose --relay-host wss://pds.robocracy.org --verify-mst --verify-basic' and it will log problems

We 💙 links! Starting this week, we've made it even easier for newsrooms and more to track how much traffic Bluesky is sending to their sites. For those setting up analytics, Bluesky's referrer is go.bsky.app.

Hey devs, this is an exciting one! Just put up an early proposal for OAuth scopes in the atproto network. Eager to hear thoughts github.com/bluesky-soci...

some group discussions i'm hoping to have at #atmosphereconf: "IndieSky": there are a few scaled-down bsky appview projects. how can we get to an out-of-box "service distribution" which people can self-host?

(system of a down voice) THE UNICITY OF OUR CITY, OF OUR CITYYYY

another huge update in here: WE FIXED THE REFERRER ISSUE 😩😫🙌👏🎉 now publishers can accurately track referrals from bluesky for any link shared in a post. hopefully this means you’ll see a large increase in the traffic that bluesky is sending to your website

Every few years, we sign up for yet another platform just to keep in touch with our friends. Private platforms have locked users in for too long, causing a lack of innovation & competition in social media. Bluesky aims to fundamentally change this. Live in 20 min with @jay.bsky.team:

👩‍💻 ¡atproto devs! 🧑‍💻 just in time for the weekend: our protocol roadmap for the first half of 2025. we got auth scopes, we got merkle tree inversions, we got deprecations, we got balmy spring weather and long walks in the forest. check it out!

new blog post: atproto by example part 1 in which I cover how to use the full potential of lexicon for building atproto apps

made some updates to 'goat', and wrote up a guide to registering a recovery key for a DID PLC, which gives better independent ownership of network identity. this is a *bit* more accessible that previously, but still oriented towards devs and power users. one small step, etc, etc

a belated happy birthday to @divy.zone

at a glance this is just a small, backwards-compatible protocol tweak. that's true, but the implications are pretty big. to date the amount of data you need to store to fully verify the next write to someone's repo grows with their repo's size. we're able to make it constant instead. but how? 1/10

🕯 🕯 🕯 🕯 atproto 🕯 relay 🕯 renaissance 🕯 🕯 🕯 🕯

I wrote up a post about how we hugely improved the write performance for Bluesky's timelines/following feed. If you want to learn more about how we did it, check it out. Some nuggets in there about embracing imperfection in some parts of a system to scale better. jazco.dev/2025/02/19/i...

I (finally!) wrote about scaling down the Bluesky AppView and how we can get to self-hosting beyond just your PDS in atproto!