this is a great and important effort! even with PLC moving out of Bluesky PBC it is important to have more replicas, especially with regional diversity and the ability to "step in" and accept ops if needed. strong endorse work in this direction. RE:

Bluesky Social

fig (aka:[phil]) (@bad-example.com)

Finally publishing this about PLC! On a day with big PLC news!! I think the news recasts this piece into more "why that's important", and less doo...

View quoted note →

excited 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 [Creating an Independent Public...](

Creating an Independent Public Ledger of Credentials (PLC) Directory Organization | Bluesky

The Bluesky Social app is built on an open network protocol that refers to each user by a unique Decentralized Identifier, or DID (a W3C standard)....

)

very cool to see AP devs hacking with AT-style OAuth! I'd really love to see convergence in the modern ecosystem around this shape of distributed OAuth RE:

Bluesky Social

Emelia (@thisismissem.social)

Ooooh, it works!! This is a client talking to an authorization server built with the `@atproto/oauth-provider` package standalone. I've implemente...

View quoted note →

to clarify if there is any confusion, Bluesky Social PBC does not currently own or control 'bluesky.app' (the domain with full "blue" in it)

anybody building on the indigo OAuth client package yet? wondering if this would already break folks or if I can sneak it in cc: @Eli Mallon [oauth: store auth req scopes s...](

GitHub

oauth: store auth req scopes same way as auth session (array of strings) by bnewbold · Pull Request #1145 · bluesky-social/indigo

This is a breaking change, and could impact database schemas or even stored data for already-deployed code relying on this package. On the other ha...

)

bsky mushroom PDS instances in us-west region are seeing flapping network issues, due to upstream provider issues

published a little guide with recommended atproto data limits and lexicon-schema-agnostic validation behaviors [Data Validation - AT Protocol](

AT Protocol

Data Validation - AT Protocol

Expectations around recommended data limits and validation.

)

"I eventually want the app to be fully independent of Bluesky" this touches on a core value for me, which is to ensure that folks can build on atproto one day at a time, and chart their own path to the future. you can start using provided tech+social infra, then grow off in a different direction [what is anisota.net? - dame's ...](

what is anisota.net? - dame's leaflets

some personal reflections and details about the future from the creator

)

AI scraping volume is centralizing the web by making "hosting a website" as difficult as "hosting your own email". even if you are fine having your site crawled, the scrapers are so aggressive that you basically need to use a CDN or tool like Anubis or be able to serve millions of req/day

go atproto devs: merged a new OAuth client SDK to indigo today. curious for feedback on the API shape! iterated on this a couple times and fairly happy how it came out. hope this makes go web app projects much easier [indigo/atproto/auth/oauth/doc....](

GitHub

indigo/atproto/auth/oauth/doc.go at main · bluesky-social/indigo

Go source code for Bluesky's atproto services. Contribute to bluesky-social/indigo development by creating an account on GitHub.

)