Bridgy pulls comments and likes from social networks back to your web site. You can also use it to publish your posts to those networks.
I’ve found a few instances in which Brid.gy will apparently fail to send a webmention (and/or fail to find a target) when the original URL contains an emoji(s). I’d suspect it’s a quirky encoding issue of some sort. I’m sure I’ve seen this issue before on Instagram where it’s probably more likely as the result of emojis in Instagram “titles” when using PESOS methods.
When I subsequently remove the emoji from the permalink, and reprocess Bridgy then has no problem finding the URL and sending the webmention. So at least there’s a “fix” on the user’s side for those experiencing this issue, but only if they’re aware it exists and have the means of executing it.
Example of failed webmention:
(I’ll note that it’s also got a fragment # in the URL, but don’t think this is a part of the issue)
Original:
Syndicated copy that was liked:
Bridgy Log:
Example of previously failed webmention that ultimately went through following emoji removal:
Original:
Syndicated copy:
Bridgy Log:
Another potential example from Instagram
Done via PESOS from Instagram which I’m sure missed webmentions (though too far back to find the specific logs):
