dangeredwolf
bsky: can't do getBlob from certain alternative PDSes (i.e. brid.gy)
Example: https://fxbsky.app/profile/funny.wetdry.world.ap.brid.gy/post/3lf67pltsb2g2
Video should load, but currently it does not because of an error returned by the default bluesky PDS
https://pds-cache.fxbsky.app/did:plc:qwrvmwksubskh6ipiybmints/bafkreibxbjjcksu2t6fqnjwpneim3fb3sfdbv5dzyot3unlpzkw7heb6gm
Going by code from cbsky, you can do a lookup on https://plc.directory/{did} (for did:plc:) or https://{domain}/.well-known/did.json (for did:web:)
@consoleSkunk I forgot to update this issue to say that most people on alternative PDSes are actually okay but whatever brid.gy is doing makes it not work.
http://funny.wetdry.world.ap.brid.gy/.well-known/did.json returns nothing either
Bridgy uses did:plc:, so the URL to lookup that account would be https://plc.directory/did:plc:qwrvmwksubskh6ipiybmints
this seems to be affecting my (friend's) PDS as well. my posts with videos don't embed their video.
what does pds-cache proxy to, out of curiosity?
ok my guess from poking is that it's proxying to https://bsky.social/xrpc/com.atproto.sync.getBlob?did=$1&cid=$2
as far as I can tell this simply won't work for any third-party PDS. the bsky mushrooms likely all work fine, but the entryway doesn't support proxying this request, so you need to always resolve the DID document and look up the actual PDS that way
... or is the issue that pds-cache currently attempts to do that, but fails and falls back to using bsky.social?