πŸ’¬ No webmentions to original URLs that include emojis

Replied to No webmentions to original URLs that include emojis (BoffoSocko)

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: F0%9F%93%85-virtual-homebrew-website-club-meetup-on-may-15-2019/?replytocom=262215#respond Syndicated copy that was liked:

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:

https://collect.readwriterespond.com/?p=10116

Rather than:

https://collect.readwriterespond.com/No+webmentions+to+original+URLs+that+include+emojis

Leave a Reply

Your email address will not be published. Required fields are marked *