- New PDS implementations would be slightly simpler - they wouldn't need to know about this fall-through behaviour (technically it's optional, but users on your PDS won't be able to use bsky without it sooooo)
Comments
Log in with your Bluesky account to leave a comment
Rolling this out probably requires careful sequencing
1. Publish a did doc for did:web:api.bsky.app with a bsky_appview service definition
2. Update the bsky app to add the atproto-proxy header to relevant requests (probably requires changes to lex-cli and @atproto/ packages)
yeah, that's all well-outlined. has not been widely advertised, but clients _can_ use our appview in exactly this way today by service proxying to did:web:api.bsky.app#bsky_appview. check it out: https://api.bsky.app/.well-known/did.json
Ah, nice. Didn't realise the did:web already existed
I might raise a PR to the bsky client to add this header in, then - being explicit would be nice and allow for third party implementations to skip implementing this fall through and continue to be able to use https://bsky.app
the did:web was only set up in the past month or two.
it has been convenient/simple in some ways to have the app.bsky.* lexicons "auto-route", but I think that "special magic" is/has become more confusing over time
Comments
1. Publish a did doc for did:web:api.bsky.app with a bsky_appview service definition
2. Update the bsky app to add the atproto-proxy header to relevant requests (probably requires changes to lex-cli and @atproto/ packages)
@bnewbold.net thoughts?
I might raise a PR to the bsky client to add this header in, then - being explicit would be nice and allow for third party implementations to skip implementing this fall through and continue to be able to use https://bsky.app
the did:web was only set up in the past month or two.
it has been convenient/simple in some ways to have the app.bsky.* lexicons "auto-route", but I think that "special magic" is/has become more confusing over time
I suspect the PR against social-app might be... big? but i'm not sure, and needs to happen at some point
right now we have to hardcode some business logic in the PDS to provide "ready sticky" behavior, which aint great