snarfed
Bluesky: not getting backfeed if syndication has DID on it
Hi,
I was having some unexpected behavior when backfeeding interactions from Bluesky. I pressed Crawl now multiple times, I checked the logs and everything seem to be correct. The logs indicated that the post had been found and te syndication URL too:
D 2025-05-30 05:26:28.900920+00:00 u-syndication links: ['https://fosstodon.org/@hacdias/114592392890260693', 'https://bsky.app/profile/did:plc:xsx3bphrwkgeo3qnfjhzmdra/post/3lqdbv6xca625']
D 2025-05-30 05:26:28.901251+00:00 processing permalink: https://hacdias.com/2025/05/10/torii/
D 2025-05-30 05:26:28.901361+00:00 previously found relationship(s) for original https://hacdias.com/2025/05/10/torii/: ['https://bsky.app/profile/did:plc:xsx3bphrwkgeo3qnfjhzmdra/post/3lqd7hyiyih2z']
I 2025-05-30 05:26:28.901711+00:00 [requests.head](http://requests.head/) https://hacdias.com/2025/05/10/torii/ {}
However, I was not getting any webmentions. I managed to solve it by changing the URL of the syndication, but I don't think that makes sense since they should've been equivalent. The issue.
- Syndication set to
https://bsky.app/profile/did:plc:xsx3bphrwkgeo3qnfjhzmdra/post/3lqdbv6xca625, Bridgy will not send webmentions. - Syndication set to
https://bsky.app/profile/hacdias.com/post/3lqdbv6xca625, Bridgy will send webmentions.
I find it a bit weird because even if I go to https://brid.gy/bluesky/hacdias.com, it redirects to https://brid.gy/bluesky/did:plc:xsx3bphrwkgeo3qnfjhzmdra, so I would assume Bridgy was prepared for this.
I assumed it is a bug, hence the issue.
Hey, sorry for the trouble! And thanks for all the details and sleuthing. Odd, we should be normalizing these URLs, below, after we convert them to at://s, so I'm curious what's going on here. Hrm.
https://github.com/snarfed/bridgy/blob/fcfad4e6e080e9b5a27ea7b6bf7e4f93075d0452/bluesky.py#L70-L75
Maybe important: this was only happening for posts that did not link to the original post. Bluesky posts with a direct link to the original content did not have a single problem.
I can try using the did: in the URLs again and see if I can reproduce the behavior.