-
Notifications
You must be signed in to change notification settings - Fork 28
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
AT to AP - Strange link, or link applied to wrong text #1123
Comments
I'm seeing the same issue with hashtags and @ mentions as well.
The first hashtag is properly mapped to a fediverse hashtag, but not the following ones. They also display a link displacement, same for the following @ mention. User page on fed.brid.gy: https://fed.brid.gy/bsky/origasky.bsky.social |
Oof, yeah. Sorry! Will fix. |
This reverts commit 85b9e19 since it caused a regression: snarfed/bridgy-fed#1123
Background: snarfed/granary@e08550e interacted badly with #990 and b4124bd. I'm rolling back snarfed/granary@e08550e, which should fix this regression, but that means AP => Bluesky profile bios still won't have meaningful whitespace, ie newlines won't show up. I'll need to figure that out. |
Sadly Mastodon's Lines 810 to 816 in 551637f
Good motivation, really I want to bring back the |
OK, the regression here should be fixed. Example: https://bsky.app/profile/snarfed.bsky.social => https://indieweb.social/@snarfed.bsky.social@bsky.brid.gy/112587591636781521 I'll leave this open to figure out the rest. |
OK, fixed preserving whitespace in AP => Bluesky bios. Example: https://bsky.app/profile/evan.cosocial.ca.ap.brid.gy |
Just ran across an odd issue I thought I would bring up here. A Bluesky post bridged over to ActivityPub has a link in a weird place.
The original Bluesky post has an @ mention for bsky.app which is displayed as a link on Bluesky. On the AP side there is no link on the @ mention, but there is a link on a different set of 9 characters.
User page on fed.brid.gy: https://fed.brid.gy/bsky/aielcakes.bsky.social
Unfortunately it doesn't look like there's a log available for that post.
The text was updated successfully, but these errors were encountered: