Skip to content
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

AP -> ATProto: mentions not resolved #1297

Open
KDederichs opened this issue Sep 1, 2024 · 2 comments
Open

AP -> ATProto: mentions not resolved #1297

KDederichs opened this issue Sep 1, 2024 · 2 comments
Labels
parity Features supported by two or more protocols, but not yet bridged between them.

Comments

@KDederichs
Copy link

I made a mastodon post while mentioning two bridged users at the same time (https://mastodon.ladon-dragon.net/@ladon/113060576389202189)
In Mastodon the handles correctly resolve to the corresponding bridgy profiles.
On Bluesky (https://bsky.app/profile/ladon.mastodon.ladon-dragon.net.ap.brid.gy/post/3l32zhupmdzj2) the user handles are just plaintext and not resolved as they should be.
(Not sure if handle resolution works in general, just something I noticed and thought maybe it has to do with the fact that there's more than one)

@snarfed
Copy link
Owner

snarfed commented Sep 2, 2024

Huh, surprising! Thanks for reporting. We've definitely had fediverse => Bluesky mentions working in general, so I'm not sure what happened here. I can look at some point.

@KDederichs
Copy link
Author

Thanks for looking into it!

@snarfed snarfed changed the title AP -> ATProto Multiple handles not resolved AP -> ATProto: mentions not resolved Sep 8, 2024
@Tamschi Tamschi added the parity Features supported by two or more protocols, but not yet bridged between them. label Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
parity Features supported by two or more protocols, but not yet bridged between them.
Projects
None yet
Development

No branches or pull requests

3 participants