AT Protocol Developers
Social networking technology created by Bluesky.
Developer-focused account. Follow @bsky.app for general announcements!
Bluesky API docs: docs.bsky.app
AT Protocol specs: atproto.com
- This transition is now complete. The 'bsky.network' firehose and jetstream instances are all functional. Connected services should have transitioned smoothly, though in some situations may require a restart.
- Having some difficulties during cutover that are affecting Relay consumers. Should be resolved shortly.
- いよいよ今日です！ あと1時間ほどで、データ伝送路を新しい中継システムに切り替える準備を進めています
- This is today! Preparing to cut over the firehose to a new relay in the next hour or so.
- 「bsky.network」で提供されている人気のファイアホースサービスが、いよいよ今週火曜日にアップグレードされます。 PDSオペレーター、ファイアホース利用者、Jetstreamユーザーへの影響は最小限に抑えられる見込みですが、詳細については全文をご確認ください。
- The popular firehose service at 'bsky.network' is finally going to be upgraded this coming Tuesday. The disruption to PDS operators, firehose consumers, and jetstream users should be minimal, but read the full post for all the details.
- Reposted by AT Protocol DevelopersWe're having an AT Proto gathering at FOSDEM, on the Friday right before, at 17h00. Come! It'll be nice and fun. luma.com/jj7nths0
- We just released Tap, a tool designed to handle the hard parts of repo synchronization, so you can focus on building your application. It's now easier than ever to stay up to date with Atmosphere records for dev, data analysis, or any other task at hand! docs.bsky.app/blog/introdu...
- interested in standardization of AT at the IETF? there are ongoing discussions happening on the mailing list, and there will be a video call this Wednesday to discuss the scope of work, especially around DIDs and identity. more details in this email thread: mailarchive.ietf.org/arch/msg/atp...
- if you are new to the IETF, the link below is a good overview of the overall process, including getting set up on the mailing list. AT (atproto) is still in the process of forming a working group, and coming to consensus on what the charter should look like.
- "Find friends by phone" is a common tool in social networks. We're proposing a secure scheme and requesting comments from the dev community. Goals: ・Double opt-in: you're not findable by your phone unless YOU use the tool ・Secure to enumeration attacks ・Resistant to decryption if compromised
- We're presenting this scheme so that software engineers can comment on potential concerns or weaknesses. If you'd like to share feedback, please use this github discussion: github.com/bluesky-soci...
- Reposted by AT Protocol DevelopersRecently we hired @jimray.bsky.team as a new devrel at Bluesky, and I wanted to give him an overview of the Atmosphere. We recorded the session! I give you: Squeeky Board with Paul and Jim, a detailed overview of AT://
- for folks working with the PLC identity system: we are planning to remove a set of non-compliant operations from the directory, which should make it easier to implement replicas and audits. these are predominantly test operations created by security researchers.
- the operations to be removed have been publicly archived, and the changes can be independently verified. we plan to execute this change in roughly a week (no sooner than 2025-11-06). you can read more in this github announcement.
- app devs: we have some new AT OAuth resources and examples for you! linked off this intro page we have new example projects showing how to do client auth using reference SDKs for TypeScript and Go. and the buried lede: an Expo library for doing AT OAuth in React Native mobile apps
- we are still cooking on docs and resources for permissions ("auth scopes"), but those will slot right in to these libraries and examples
- Reposted by AT Protocol Developersatmosphere devs! 🧑🚀 just published a protocol checkin: docs.bsky.app/blog/protoco... tl;dr expect to see a lot of updates from us in the next few months. we're hard at work on making AT easier to build on & ensuring the network remains a resilient foundation for the future of open social
- Reposted by AT Protocol Developersokay 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...
- All services should now be recovered!
- An upstream network problem has been impacting almost all Bluesky network services for the past 3-4 hours. Posting and other public interactions are disrupted for many accounts. As connectivity recovers, the firehose and other services will see large surges of events.
- Reposted by AT Protocol Developersvery excited to share this update about bringing AT to the IETF! last week we uploaded two drafts to the IETF datatracker and today we heard that we’re approved to host a Birds of a Feather at IETF 124 (the formal meeting towards establishing a working group)
- Reposted by AT Protocol Developersexcited 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.
- Reposted by AT Protocol DevelopersAdversarial 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
- We hope this sheds some light for app devs on some protocol design decisions which have caused some friction. We'll have a separate update soon summarizing recent improvements to the OAuth developer and user experiences
- 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
- The internet was meant to be free - your identity shouldn’t be locked behind a login screen. Introducing bsky.storage 🐔🤝🦋 Now you can back up your Bluesky data hourly + recover your account if Bluesky ever goes dark. Simple, free, & fully in your control. Learn more: medium.com/@storacha/in...
- 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!
- Reposted by AT Protocol Developersfresh 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
- Reposted by AT Protocol DevelopersThis 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
- Reposted by AT Protocol DevelopersJay 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
- Reposted by AT Protocol DevelopersHey 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...
- Reposted by AT Protocol DevelopersSeemed like a good moment to launch 3 minute videos! (Pressed the button from the audience!)
- Reposted by AT Protocol Developers👩💻 ¡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!
- Reposted by AT Protocol Developers🏷️ 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
- Reposted by AT Protocol DevelopersHowdy 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 🤞🏼!
- Our first ever Bluesky meetup in Austin🦋 thanks @pfrazee.com for joining and @meetdliu.bsky.social for organizing💙
- Reposted by AT Protocol Developers🛠️ 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
- Reposted by AT Protocol DevelopersI 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...
- Reposted by AT Protocol Developersin an hour!
- Reposted by AT Protocol DevelopersLong press the version number in settings to enter developer mode, you'll get new options on posts and profiles
- Reposted by AT Protocol DevelopersIf 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
- Reposted by AT Protocol DevelopersI'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
- Reposted by AT Protocol DevelopersI 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:
- Reposted by AT Protocol Developers🚀 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.
- Reposted by AT Protocol Developers🎉 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...
- Reposted by AT Protocol Developersvery unfortunate CBOR parsing bug this likely broke all firehose consumers using the Typescript libraries just published the fix: github.com/bluesky-soci...
- Looks like it. There's a bug in atproto it seems, and it's making all new posts be dropped. Will try to fix it as soon as I can! 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.
- Reposted by AT Protocol Developerskudos 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...
- Reposted by AT Protocol DevelopersI'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...
- Reposted by AT Protocol DevelopersInitial 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
- Reposted by AT Protocol Developers
[This post could not be retrieved] - Reposted by AT Protocol Developersmentions tab has been a much-requested feature, looking forward to it :)
- New PR: Notification filtering (#3224)
- Reposted by AT Protocol Developers🔥 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... 🧵👇
- Reposted by AT Protocol Developers#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...
- Reposted by AT Protocol DevelopersI 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.
- Reposted by AT Protocol DevelopersSource code: github.com/czue/bluesky...
- Reposted by AT Protocol DevelopersThe 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
- Reposted by AT Protocol DevelopersWhile Bluesky looks like other social apps on the surface, it’s actually quite different. It’s an open network. I blogged about it here:
- Reposted by AT Protocol Developers#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
- Reposted by AT Protocol Developersone 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
- Reposted by AT Protocol Developersthere 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
- Reposted by AT Protocol Developerssome 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)
- Reposted by AT Protocol Developersif 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.
- Reposted by AT Protocol Developerswe 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
- Reposted by AT Protocol Developersit'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). 🧵
- Reposted by AT Protocol Developers#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...
- Reposted by AT Protocol Developersrelay 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)
- Reposted by AT Protocol DevelopersHello, world! Send from millipds, an atproto PDS written in Python (and a concerning amount of C)
- Reposted by AT Protocol Developersok, let's break it down. at the core of atproto is the data. it lives own your own computer (or someone hosts it for you). think of it as a hard drive with JSON files on it data is structured (i.e. has a type), and can references other records on other peoples' computer with a URI like a hyperlink
- Reposted by AT Protocol Developersprivate content is one of the top asks of atproto, we have some ideas. leading designs involve each user having multiple private repos. they differ from your public repo as they are access-controlled and not signed/redistributable. but they are still key->value, addressable, and of course they sync!
- Reposted by AT Protocol Developers#atproto devs! want to give an early heads up that we have a bunch of relay work in flight: fan-out pseudo-relays, bigger server, and more. these don't touch the wire protocol, but might result in new relay hostnames, and in particular reset cursor values
- Reposted by AT Protocol DevelopersLove this @atproto.com protcol browser, it lets you see everything you've ever done since you been here. For me it's Bluesky, My Blog, Front-page and even Picosky!
