@help I've noticed that my webmentions from my self-hosted WordPress to micro.blog are no longer functioning properly. It's like they went on a little vacation or something. I'm unsure what caused this change, but it’s a new wrinkle.

Here's an example: I recently replied to a comment via my WordPress blog (you can check it out here), and I used the recommended method for webmentions to link it to the corresponding comment on micro.blog (here). Normally, this works like a charm, but this time, the reply didn't appear on the micro.blog.

Here's another example. I replied on my WordPress blog to a comment (here), and once again, the webmention didn't reach its destination on micro.blog (here).

I'm curious if something changed on the micro.blog side that could have caused this. It could also be a compatibility issue with updates to the IndieWeb plugins on my self-hosted WordPress setup, but I’ve not had any issues with this in the past.

I've grown fond of Webmentions as they allow me to connect with the community on micro.blog, so it's a bummer to see them go wonky.

@help do you have any update on this? I use this exactly as written on the documentation page.

For blogs hosted externally to Micro.blog, such as with WordPress, you are responsible for linking usernames for Micro.blog users you want to mention. Just including @username without a link will have no effect. It should be something like <a href="https://micro.blog/username"><a href="https://micro.blog/username">@username</a></a> to indicate to Micro.blog that a specific user should be notified. Micro.blog does not automatically link any text in external blog posts. (By adding links yourself, posts will show up correctly not just on Micro.blog but also on your web site and in feed readers.)

I tried manually pushing the Webmention with curl.

curl -i -d source=https://islandinthenet.com/reconsidering-choices-reflecting-on-the-lectric-xpremium-electric-bike-experience/#comment-31170 -d target=https://micro.blog/Denny/21869905 https://micro.blog/webmention

I got the following response.

HTTP/1.1 202 Accepted server: nginx/1.14.2 date: Thu, 10 Aug 2023 13:12:11 GMT content-type: text/html;charset=utf-8 content-length: 0 connection: close

I didn’t find any errors in my logs.

@khurtwilliams I'm looking into this and it does appear there's an error on the Micro.blog side because it's hitting something unexpected. Hopefully something we can fix.