one thing I do like about the Following / replies change discussion is that it seems everybody is on the same page that defaults matter, and that the default/popular experience impacts the whole network.
rollercoaster of a day!
the bluesky relay is holding up fine at the moment, but a couple infra notes:
would be great if consumers can set a user-agent so we can informally differentiate and understand load patterns
backfill requests are more expensive than keeping up with stream
rolling out basic AP support a small step at a time works very effectively for PR!
I know facebook claims this is about legal/reputation risk, but i'm pretty skeptical. they have found a way to get positive press over a multi-year time frame for very little practical interop (and zero adversarial?)
RE:
trying to implement atproto OAuth in an SDK or new language?
got a draft implementation guide up, interested in feedback.
(hopefully most general devs won't have to get in to these details+acronyms; just use an SDK!)
[github.com/bluesky-social...](📃.md )
atproto devs!
we are rolling out a small set of changes to OAuth: some required scopes, DPoP needs to start at PAR, and removed some openid/OIDC stuff. client packages, PDS self-hosting, and prod PDS/entryway all getting updates
may disrupt early demos, but should be more stable after this.
trying to channel wendy hanamura "joy of missing out" energy having not been at either dweb camp or xoxo this year.
more events soon, hopefully!
where should I, or other bsky folks, show up?
legit seems like "federation" terminology seems to be causing more confusion than understanding for atproto.
I think it was maybe helpful earlier on, but less now. would changing the terminology feel like a helpful clarification or a rug-pull?
