You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that Bluesky is internally federating, I'm thinking about how to handle that. Right now, Client either takes a single explicit server or defaults to bsky.social. Should we also support per-call server discovery based on the target repo's DID doc? Seems useful, but we'd have to determine the target repo for each call, which there's no call-independent way to do afaik, and some calls are PDS-level (not repo-level) anyway. Hrm.
The text was updated successfully, but these errors were encountered:
snarfed
changed the title
Clients: PDS discovery
Clients: PDS discovery?
Nov 10, 2023
snarfed
changed the title
Clients: PDS discovery?
Client: PDS discovery?
Nov 11, 2023
Now that Bluesky is internally federating, I'm thinking about how to handle that. Right now,
Client
either takes a single explicit server or defaults to bsky.social. Should we also support per-call server discovery based on the target repo's DID doc? Seems useful, but we'd have to determine the target repo for each call, which there's no call-independent way to do afaik, and some calls are PDS-level (not repo-level) anyway. Hrm.The text was updated successfully, but these errors were encountered: