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: @npub1tgqc...20nv [oauth: store auth req scopes s...]( )
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]( )
"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 ...]( )
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....]( )
damn they are really cooking over there RE: View quoted note →
having to click through a bunch of unwanted AI feature modals is the USA version of GDPR cookie banners
I built a demo atproto app for exploring the combination of "user intent" declaration records and the proposed AI-PREF vocabulary and HTTP headers which pass the preference through to crawlers (eg, AI companies) [ATProto User Intents Demo]( )