mpv 'https://pds.dev.retr0.id/xrpc/com.atproto.sync.getBlob?did=did:plc:t423oqsrtl5gtgdfxvye5gco&cid=bafkreieb7c45qi6qgebqi276y3m35w5vbmy57afpsoussgj7qtzkm3kd3q'
mpv 'https://pds.dev.retr0.id/xrpc/com.atproto.sync.getBlob?did=did:plc:t423oqsrtl5gtgdfxvye5gco&cid=bafkreieb7c45qi6qgebqi276y3m35w5vbmy57afpsoussgj7qtzkm3kd3q'
- the C programming language
- the C programming language
everything works, except for the things that don't work
everything works, except for the things that don't work
there are no new user-facing features, but under the hood we're doing real DID resolution now. This means atproto service proxying is fully implemented, with nothing hardcoded.
there are no new user-facing features, but under the hood we're doing real DID resolution now. This means atproto service proxying is fully implemented, with nothing hardcoded.
- resolveHandle works for external handles (by forwarding to appview)
- putPreferences/getPreferences works
- bsky appview proxying uses wildcard matching so I don't have to keep updating a list of endpoints
- resolveHandle works for external handles (by forwarding to appview)
- putPreferences/getPreferences works
- bsky appview proxying uses wildcard matching so I don't have to keep updating a list of endpoints