On did:web accounts (such as @zio.sh or @didd.uk) the avatar doesn't load.
Screenshot: https://blob.ducky.ws/bafkreife7x5howrccpaoug4ultks3rtnfns2acrjr33j3vp3zjizusrnea
On did:web accounts (such as @zio.sh or @didd.uk) the avatar doesn't load.
Screenshot: https://blob.ducky.ws/bafkreife7x5howrccpaoug4ultks3rtnfns2acrjr33j3vp3zjizusrnea
Noticed you're pulling it from the CDN (appview/state/state.go#830). Do wonder if its setup to maybe mitigate a large amount of requests from there? Probably a better idea to just pull the blob directly from the PDS (i.e. https://zio.blue/xrpc/com.atproto.sync.getBlob?did=did:web:zio.sh&cid=bafkreid7nyjc5eznloxfmmptd7a5r753fxxf2xnmgbcpmgspq5izf3u54u)
this was the initial approach; unfortunately the go api mandates auth for some reason. there should be a better way.
Huh, interesting. As far as I'm aware, however, com.atproto.sync.getBlob never requires authorization (and there seems to be no way to force it), so it could literally be a case of doing fmt.Sprintf("https://%s/xrpc/com.atproto.sync.getBlob?did=%s&cid=%s", pds, did, link) instead of using the CDN URL
Okay, yeah this is now fixed and deployed but it's considerably slower. We might have to put a cache on top of these ourselves…
It’s not necessarily did:web from what I’ve seen (mine doesn’t load ironically, and it’s did:plc). There’s an issue with how we fetch it I think since we get a 400 on some profiles.