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

Quick update on Auth Scopes! Covering the granular permissions roll out for end users and client app devs. Permission Sets and formal specifications are still being worked on. We recommend devs start exploring and experimenting, but hold off on shipping major production app updates for now.

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

we just published an updated proposal for "Auth Scopes", and are interested in your feedback! this is a mechanism for OAuth clients to request granular permissions to PDS resources. for example, only write repo records of specific types, or only authenticate to specific remote endpoints

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

Two types of OAuth client are supported by atproto: "public" and "confidential" This new article digs in to the security trade-offs and safety mechanisms at play, and how they impact different app architectures: TMBs, BFFs, SPAs, etc

bsky.storage is an independent project that automates periodic account data backups to a storage network, and has a UI for PLC identity backup and recovery tools like this give users stronger control of their online future, without needing to self-host an entire PDS

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

we've got a new proposal up with more Ozone moderation report reasons! if you run a labeler, or develop a client which submits mod reports, take a look, and leave feedback on the linked Github discussion

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!

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

This is an article that I've wanted to write for over a year, and I finally got the chance to do it! Atproto Ethos is a deep dive into how we think about protocol design - its influences, the core innovations, and the opinionated takes that we've adopted

Jay Graber @jay.bsky.team, CEO of Bluesky, gave a few remarks before lunch on Saturday. "The AT Protocol here is what is fundamentally different, and because you're here today, you're different." #ATmosphereConf

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...

Seemed like a good moment to launch 3 minute videos! (Pressed the button from the audience!)

👩‍💻 ¡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!

🏷️ devs and mod service operators! 🏷️ got a proposal up about moderation report routing. this is basically a small update to let moderation services ("labelers") declare what kind of reports they are willing to receive. implementation on this is under way and we hope to ship it soon

Howdy Austinites! Think it’s time to organize another meetup. With @jay.bsky.team in town for #SXSW, curious if the bsky fam would be interested in a meetup on Monday, March 10? Please reply if you’re interested and I’ll get a formal RSVP save the date going. Can’t guarantee she’ll join us but 🤞🏼!

🛠️ atproto devs! 🛠️ got a new proposal out about Sync 1.1, aka inductive firehose, aka cheap validating relays. it is a long, low-level doc. doesn't directly impact folks unless they emit a firehose (eg, PDS and other repo hosts), or are doing full validation as a consumer

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...

in an hour!

Long press the version number in settings to enter developer mode, you'll get new options on posts and profiles

If you're an engineer that's curious about what it's like to scale Bluesky, give this pod a listen! Autumn and Justin are such fun hosts too

I've just released pleasenox.com – Convert any x.com thread to Bluesky 🦋 #indiehackers #buildinpublic #twitter – Perfect for those who have left Twitter but wish to comment upon a thread there

I just published a write-up over on my blog about how I created my new automated dynamic Bluesky avatar that changes every hour of every day. 🌅 See the project's inner workings and take a look at my creative process here:

🚀 Just released a new version of our TypeScript SDK for Bluesky! This update brings important improvements to the typings of our data model, making integration smoother and more reliable. Learn a thing or two about Bluesky’s API and the AT Protocol in the blog article we wrote for the occasion.

🎉 We’re bringing you a bunch of new Bluesky tools! 🚀 🦋 Track growth 🦋 Manage followers 🦋 Measure engagement See deeper stats to build a thriving community that’s truly yours. ✨ See more: fedica.com/blog/bluesky...

very unfortunate CBOR parsing bug this likely broke all firehose consumers using the Typescript libraries just published the fix: github.com/bluesky-soci...

2024 was a big year for atproto! We've got an update looking back at progress that has been made, and some protocol work in progress. Will have a 2025 roadmap to share soon.

kudos to @retr0.id's millipds project helping turn-up some subtle issues on the bsky appview's indexing path. some self-hosted repositories were landing in a backfill path and getting stuck there. it's looking like this wrinkle has been worked out! more details here: github.com/bluesky-soci...

I'm excited to announce @skyseed.fund, the world's first incubator & fund exclusively focused on Bluesky and @atproto.com. We're just getting started but have $1 Million in committed capital, and will be doing developer grants as well as pre-seed/seed funding. www.prweb.com/releases/ope...

Initial call for interest: want to get involved in an #atproto in-person conference, late March in the Pacific Northwest? Read the info at atprotocol.dev/atmosphereco... and please fill out the form to give feedback #ATmosphereConf

I spent this week building bluetube.fyi using the Bluesky firehose to aggregate YouTube videos. I have plans to layer on more discovery features and more content providers - please let me know your thoughts!

mentions tab has been a much-requested feature, looking forward to it :)

🔥 Open APIs power the web! Thanks to @bsky.app's powerful API we were able to build a deep integration that lets anyone automate workflows with Bluesky. For inspiration check out examples below, or learn more about all 10 triggers/actions here: www.relay.app/apps/bluesky... 🧵👇

#atproto devs! have two new specification drafts up. first is "Data Synchronization", covering the firehose: github.com/bluesky-soci... second is "Account Hosting", covering account migration and lifecycle: github.com/bluesky-soci...

I made a Chrome Extension to bring Bluesky comments to any URL :) Get it here: github.com/joneslloyd/b... Credits to: - @emilyliu.me - @coryzue.com - @louee.bsky.social Any feedback and/or PRs are welcome. I threw this together in 1.5 errors, so expect bugs etc.

Source code: github.com/czue/bluesky...

The fastest growing app on the App Store is fully open source. You may have heard of it. But do you know how it works? I do now! Huge thanks to everyone who helped me make this one happen 🙏 youtu.be/cIoYUQhKJUo

While Bluesky looks like other social apps on the surface, it’s actually quite different. It’s an open network. I blogged about it here:

#atproto devs and protocol folks! looking for feedback on options for Lexicon Resolution. we have a broad sketch, but still some open questions and truely not sure which way we are leaning

one category of events did *not* come through: account events have be getting dropped on the public firehose for a couple days now. identity events were going through. we don't currently have a plan to re-emit/replay those account events. if possible, might be prudent to re-fetch account state

there were *a lot* of duplicate events at various times. the firehose was re-broadcasting itself at multiple times the normal rate for a while. oops! we also re-ran events for a couple hours from a couple PDS instances to ensure all events came through on the main firehose

some more details on public firehose stuff: you can/should reconnect now! note that the sequence is different (lower, like 274908607-ish at the moment) if you scroll back to the start of this backfill window, consumers *should* see all events (aka, not miss anything)

if you are a firehose consumer, you'll need to update cursor to this new sequence space. you will probably see duplicate/overlapping events. there may be a few other bumps in there, like tooBig, and a spike from a couple PDS reconnects.

we have thrown out our earlier plans for now, and have cut over the bsky.network public firehose endpoint to our alternative relay. we have rolled the cursor back about 4 hours of wall-time, and it is catching up to current. this is a new cursor sequence! 251476547 is a random recent seq

it's been a rough couple hours for the firehose! it has been flapping around in volume and offset. the bsky app has been smoother because we are using an alternative internal relay (starting a couple days ago). 🧵

#atproto devs and firehose consumers! we have changes coming soon with our relay service, which will result in a sequence number reset/update. all that and more inside...

relay is a bit bumpy right now. may see some connections dropped. we are working to squeeze out a bit more capacity on the current relay, and have a replacement and other mitigations coming (will post more details soon)