Open snarfed opened 11 months ago
Sounds like this isn't actually a priority until real federation. From https://github.com/bluesky-social/atproto/discussions/1832 :
Client apps, bots, and other integrations can continue to connect to bsky.social as an API endpoint, and requests will be proxied to the appropriate endpoint. They do not need to connect directly to the account's PDS for now, especially for authentication (login and session refresh)
Most of the work here will probably happen in https://github.com/snarfed/lexrpc/issues/4
Bluesky is federating internally, and it's hitting us! 😁 https://github.com/bluesky-social/atproto/discussions/1832 . We need to start resolving handles and DIDs to users' individual PDSes and make calls to them instead of bsky.social, or at least auth calls and get timelines etc from the prod AppView api.bsky.app. Not sure which we'll prefer. cc @JoelOtter