As promised a couple evenings ago, I've written up my approach to implementing the app.bsky.actor.getProfile endpoint
My Appview - the first xrpc endpoint
willdot.leaflet.pubSep 3, 2026 at 6:44 PM
app.bsky.actor.getProfile | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually proxied via the user's PDS, using service proxy headers. Authenticated requests can be used for both public and non-public endpoints.*
app.bsky.actor.searchActorsTypeahead | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user's PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.*
app.bsky.notification.getPreferences | Bluesky
*This endpoint is part of the Bluesky application Lexicon APIs (`app.bsky.*`). Public endpoints which don't require authentication can be made directly against the public Bluesky AppView API: https://public.api.bsky.app. Authenticated requests are usually made to the user's PDS, with automatic service proxying. Authenticated requests can be used for both public and non-public endpoints.*
Bluesky social oauth scope "Bad token scope"
I'm trying to build an app that integrates with bsky's OAuth and API. Using the below the document using the "Browser App" option. https://docs.bsky.app/docs/advanced-guides/oauth-client ...
Where Are The Exits?? · thoughts
What the AT protocol needs from Bluesky PBC now, and why it's not to focus on bsky.app
bsky.md — Bluesky as Markdown
Fetch any public Bluesky content as clean, portable Markdown. No auth, no API key.
When @bsky.app pulls this kind of crap often, whilst also expecting the community to do the heavy-lifting in actually convincing people to try out the AT Protocol... it's really difficult to feel hopeful about the future of Bluesky and its constituents. I imagine many agree with this stance.
Rude1 Haunted Badness. ⁂
Bluesky’s statement deriding Threads users as “guinea pigs” is not representative of Blacksky Algorithms, the atproto ecosystem or the open social web more broadly. Communities form around communication networks. And communities should never be trolled for whatever tool helps them find each other.
new from me: an API to return bluesky data as markdown! bsky-md.vercel.app open source on Tangled too! tangled.org/j4ck.xyz/bsky-md
bsky.md — Bluesky as Markdown
bsky-md.vercel.apphaven't felt this energized in a while 🔋 We're building a proof-of-concept E2EE library & demo on AT Protocol, using BeeKEM for DCGKA. There's a long road between a PoC and a foundation we can all depend on, but every journey has a first step🐾 bsky.app/profile/boscolo.co/post/3m52h… bsky.app/profile/expede.wtf/post/3mraq…
chrisb
With #AT-SMS we are committed to building group messaging support on top of the most promising decentralized continuous group key agreement (DCGKA). No candidates yet, tho. I think a few more implementations are needed to make the IETF discussions fruitful. bsky.app/profile/boscolo.co/post/3lwuh…
happy Monday, I wrote up my decision-making around our new endpoints.bsky.app HTTP reference! Thanks everyone for the push to do this 😊
About the new endpoints.bsky.app
alex-bsky.leaflet.pub
