-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turn off serving AS2 actors (at least non-web) via /r/
URLs
#1654
Comments
Interestingly, fetching |
Oh wow, interesting. Yeah, we probably shouldn't be serving AS2 actors for paths like these at all. Out of curiosity, do you know where this fetch came from? Ie, do you know where https://bsky.brid.gy/r/https://bsky.app/profile/sanhwa-lee.com or https://bsky.brid.gy/r/https://bsky.app/profile/did:plc:xmbyi47sypz7q2mx5j7ay6sl originally appeared as ActivityPub-fetchable ids? |
It didn't appear really, I wanted to follow this user (saw in bsky) and that didn't work so I started debugging 😄 |
Ah ok, thanks for the explanation. That user hasn't enabled the bridge, so you can't follow them from the fediverse yet. Congrats on finding an unusual way to convert part of their profile to AS2 though! Similar to https://granary.io/ , I guess. I'll keep this issue open to track turning that off. |
I see ap.brid.gy in the followers list though 👀 |
OK! They're not actually bridged though: https://fed.brid.gy/bsky/did:plc:xmbyi47sypz7q2mx5j7ay6sl . Maybe they followed ap.brid.gy before their profile was fully set up and satisfied https://fed.brid.gy/docs#troubleshooting, or maybe during an outage like #1520. Feel free to ask them to try again! |
bsky.brid.gy/r/
doesn't give did-based ID for some users/r/
URLs
Oh no, so I won't be able to (ab)use the /r/ url to resolve bsky URLs? I find it useful 😢 |
Hah, sorry. It'll still work for Bluesky post URLs, if they're bridged! And you can find a bridged Bluesky user by their Webfinger, |
Unclear why. Together with #1653, this means there's no mean to get inbox URL.
The text was updated successfully, but these errors were encountered: