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)
Syndicated copy that was liked: https://twitter.com/ChrisAldrich/status/1129124049068498944#favorited-by-14591484
Bridgy Log: https://brid.gy/log?start_time=1558056830&key=aglzfmJyaWQtZ3lyTAsSCFJlc3BvbnNlIj50YWc6dHdpdHRlci5jb20sMjAxMzoxMTI5MTI0MDQ5MDY4NDk4OTQ0X2Zhdm9yaXRlZF9ieV8xNDU5MTQ4NAw
Example of previously failed webmention that ultimately went through following emoji removal:
Syndicated copy: https://twitter.com/ChrisAldrich/status/1129124049068498944#favorited-by-19844672
Bridgy Log: https://brid.gy/log?start_time=1558714459&key=aglzfmJyaWQtZ3lyTAsSCFJlc3BvbnNlIj50YWc6dHdpdHRlci5jb20sMjAxMzoxMTI5MTI0MDQ5MDY4NDk4OTQ0X2Zhdm9yaXRlZF9ieV8xOTg0NDY3Mgw
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):
3 thoughts on “No webmentions to original URLs that include emojis”
filed https://github.com/pfefferle/wordpress-webmention/issues/199 . tentatively closing; feel free to reopen.
This issue with webmentions and emojis is the reason when I manually set each slug, because what I was finding was that my posts were not pinging. However, when I used the permalink then it worked. For example:
issue is a special kind of article post that is a reply to typically some source code, though potentially anything at a source control repository.