Yeah I was just wondering what I need to do on the server side to make this work, like this?
Yeah I was just wondering what I need to do on the server side to make this work, like this?
A service ID that is uniquely identified in the DID document.
I think I'm still missing something⦠so I have this definition: blue.mackuba.eu/.well-known/.... I reused the existing `#bsky_fg` there. I'm making a call to my PDS with /xrpc/blue.feeds.lycan.printToken and headers { 'atproto-proxy': 'did:web:blue.mackuba.eu#bsky_fg' }.
I receive this request from the PDS IP on blue.mackuba.eu on that path, but without any auth headerβ¦
Fuck, nevermind, Ruby error π«£ ENV vs. envβ¦
lol my PDS shows a diff error for that - jglypt.net/.well-known/...
Yeah PDS doesn't have its own "identity" as a DID I guess, feed generators do