July 2026 update for the atproto implementations tables. ➡️ github.com/threddyrex/atproto-links I refreshed the PDS and AppView data, and added a new table for Relays. There are 23 PDSs, 4 AppViews, and 5 Relays.

As far as i understand the #atproto ecosystem has 3 great problems: 1) the main huge relay is under control of #bluesky 2) The #PLC (identity register) is under control of the same company 3) also the protocol itself is developed and at the moment under control of bluesky.

Can everyone building on atproto please answer this question? 😇

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)

the critical thing that got me on board with atproto is relays incrementalize sync of the entire dataset, which eliminates polling when crawling the old web is currently being crushed under crawler load and I don't think it's going away, so I think atproto is the only way to save the open web

atproto devs, read this:

I have heard from our favourite network layer protocol madman that unexpected atproto integrations are occurring. No, lower level than you’re thinking.

the single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews