for other atproto ecosystem folks: most things are working smoothly, but you may be seeing slow (high p99) handle resolution (via HTTPS well-known) for *.bsky.social handles (even projects which don't rely on bsky services often need to resolve handles as part of interop)
Bluesky Status
We are seeing elevated errors and timeouts on some Bluesky-hosted services, and are investigating.
Apr 20, 2026 at 8:01 PM
ATPROTO isn’t just for Bluesky weiners
Welcome to the new atproto.com - AT Protocol
We've updated just about everything about atproto.com to make it easier for developers to just build things.
atpotato
creating fun apps, helpful tools, and approachable content for the atproto and bsky ecosystem
Call for Developer Projects · bluesky-social atproto · Discussion #3049
The last few weeks have seen a swell of developer interest in atproto. Welcome! The protocol is maturing, and now is a great time for early adopters to jump in and start building. This post lists s...
atproto/packages/dev-env at main · bluesky-social/atproto
Social networking technology created by Bluesky. Contribute to bluesky-social/atproto development by creating an account on GitHub.
b5 (@b5.bsky.social)
Ok, a rundown of how we get p2p ATProtocol going: 1. Run *standard* ATProto services, locally 2. Use p2p to holepunch TCP connections 3. Add a thin layer for peering management Bundle all that up in an app, and we have a recipe for adding resilience & scaling to Bluesky. 🧵 teim:
What is atproto?
What is atproto? atproto is two things: A protocol for creating open social networks An open social network atproto, the open social network Today the atproto network has 36+ million users and powers Bluesky and a handful of other apps. Almost all atproto data is public. Content like posts, likes, follows, and photos/videos are publicly accessible to any network participant in a permissionless way. As an example of how open the network is, here’s how easy it is to stream all public data on the network using a public atproto Relay like bsky.network:
dietrich (@burrito.space)
@why.bsky.team how locked to the http+dns+ssl nexus of publisher-centric control is atproto? i see https noted briefly in xrpc docs. how local+offline and transport agnostic can we get here? bluetooth / mdns / laser / pigeon transports possible?
For the past six months @mariaa.bsky.social and I have been working on creating an improved research experience on atproto. It's now live! Check out: lea.ac
Lea: research-oriented social media
leaflet.pubI'm building on atproto because building infrastructure like "Drafts and Scheduled Posts for every atproto app" is easy as 1-2-3 and as cool as alf. Announcing alf, the atproto Latency Fabric: leaflet.pub/p/did:plc:3vdrgzr2zybocs45yfh…
a stuffed animal wearing sunglasses and a shirt is sitting at a keyboard .
media.tenor.comIt's hard for non-technical people to understand that #atproto (Bluesky, and friends) really is a different breed of social software. One where our data, and connections are no longer taken hostage by the platform and we're free to store our data wherever we want
Actually I don't think #atproto is about decentralization. It's more about indexing over distributed data. @bsky.app and @tangled.org are actually a centralized service just like general web search engines are. But just like search engines, we don't own your content and this is the important part. 🧵
Theo
👀👀 To be clear I’m very into decentralized tech and atproto is very cool, I just don’t love shoving it into everything and don’t see it as valuable in a use case like GitHub I’m down to be convinced
