atproto devs! this is a small one: we are updating the NSID syntax to allow non-leading digits in the final 'name' segment. this makes 'com.example.postV2' a valid NSID (it wasn't before). this will take a while to roll out everywhere, and will be "broken" until it works everywhere... [NSID: allow digits in 'name' s...](

GitHub

NSID: allow digits in 'name' segment by bnewbold · Pull Request #402 · bluesky-social/atproto-website

Closes: #391 indigo (golang) PR: bluesky-social/indigo#981 atproto (typescript) PR: bluesky-social/atproto#3633 interop tests PR: bluesky-social/at...

)

got a new proposal up for web policy wonks! calling these "User Intents" this is a mechanism to let atproto users declare their preferences around certain categories of data use, like generative AI, public access archiving, bulk datasets, and protocol bridging [github.com/bluesky-social...](📃.md )

👩‍💻 ¡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! [2025 Protocol Roadmap (Spring ...](

2025 Protocol Roadmap (Spring and Summer) | Bluesky

Join the Github discussion here.

)

'com.atproto.lore.*'

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 [Registering Identity Recovery ...](

Registering Identity Recovery Keys via PDS, using goat | bryan newbold (✈️ vacation/travel through mid-Jan)

One of the big design goals for atproto is for users to "own their network identity". If something goes wrong with a hosting provider, it should be...

)

is there an image labeler for those instagram posts which are just text on a solid color background

we are finally going to fully nuke the `#handle', '#tombstone', and '#migrate' events from the firehose. these have been deprecated in favor of '#identity' and '#account' for a long time now

🏷️ 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 [proposals/0007-mod-report-rout...](

GitHub

proposals/0007-mod-report-routing at main · bluesky-social/proposals

Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.

)

probably need to write tutorial on how to publish Lexicons with the new lex resolution stuff. here is the short version! say you have new lexicon record type with NSID 'dev.example.drink.tea', and you control the 'example.dev' domain name

🛠️ 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 [proposals/0006-sync-iteration ...](

GitHub

proposals/0006-sync-iteration at main · bluesky-social/proposals

Bluesky proposal discussions. Contribute to bluesky-social/proposals development by creating an account on GitHub.

)