Max Glenister

Blog & IndieWeb • 3 min read • 37 interactions Plain text

Adding support for Webmentions

Part 1 of 4 · Webmentions

I’ve added Webmention support to the posts on this blog.

Webmentions are a method for websites to know that they’ve been linked to (or mentioned) from elsewhere on the web.

Webmention is a web standard for mentions and conversations across the web, a powerful building block that is used for a growing federated network of comments, likes, reposts, and other rich interactions across the decentralized social web.

When you link to a website, you can send it a Webmention to notify it. If it supports Webmentions, then that website may display your post as a comment, like, or other response, and presto, you’re having a conversation from one site to another!

It depends on a couple of things being in place for it all to work, but I’ve implemented the basics to fetch and display any mentions that have been detected by the webmention.io service.

I have already been using Github Issues-powered commenting for the past couple of years, so I took the time to consolidate comments and Webmentions in to a single chunk of “interactions” functionality to fetch, cache, and render any comments or Webmentions. This is all done with native JS and could probably be improved further with a framework like Vue.js, but it works fine for now.

I’m using brid.gy to recieve Webmentions from Twitter and Reddit interactions via webmention.io — this will mean that if somebody shares/likes/retweets a link to one of my blog posts on either platform it will display that here below the post.

I’m using webmention.app and IFTTT to automatically try and send webmentions to sites I link to from within my posts.

As you can see it’s a bit complicated, and it feels like it’s held together with duct tape in places, but for now it works!

Lots of others have written about how they’ve implemented Webmentions on their sites, and these write-ups were really useful when arriving at my own implementation.

So to share the love, here are some links to those posts:

And that’s about it really. I’ll be tweeting a link to this post once it’s published and then any replies or likes will hopefully appear at the bottom of the page.

  • Blog & IndieWeb · shares #indieweb
    Enriching webmentions from third-party platforms

    I keep finding new gaps in my webmention implementation. Mentions coming in from Bluesky, Lemmy and Lobsters were showing up with no author at all, just a blank avatar and an empty name. Reddit and Hacker News bookmarks fared a bit better, with a username attached, but got flattened into a generic “bookmarked” icon with no indication of where the post had actually been shared. Lobsters mentions also carried the wrong published date. None of these felt like they were pulling their weight compared to a proper webmention from a blog or Mastodon.

    June 2026 • 8 min read
  • Blog & IndieWeb · shares #indieweb
    A Bit of a Bodge To Make MASSIVE Emoji

    I’ve been fiddling with an instance of Known over on social.omgmog.net. As part of my fiddling I’ve been trying out some of the plugins for Known. I came across the “Render Emoji Unicode” plugin but it was using an old library, and referencing an old version of Twemoji, so I updated it to use the latest Twemoji library.

    May 2022 • 3 min read
  • Web Dev · shares #programming
    The woes of trailing commas in IE

    If you leave a trailing comma in your JavaScript code, you’re a terrible person. It’s right up there with omitting semicolons as far as I’m concerned.

    November 2012 • 2 min read

Discussion

14 likes
  • JB
  • JB
5 reposts
  • 📢 My blog now supports #webmentions! It's held together with duct tape, but it should all work... Interactions with this tweet should appear on the post blog.omgmog.net/post/adding-su…
  • If all of this Webmention malarky is overwhelming for you and you just want to drop a nice reply, feel free to do it on the Github issue

  • Reply on twitter.com · 8 April 2022

  • Reply on queer.party · 27 April 2022

  • Reply on indieweb.social · 27 April 2022

  • @trainingmontage It's a great yak to shave! There are a number of implementations to make the process easier, but it's quite fun rolling your own too! ⌨️ 🔥

  • Reply on indieweb.social · 27 April 2022

  • @m2m Yeah I imagine it's fine, but I can't help but worry that it depends on so many moving pieces, and two external services (webmention.io, and brid.gy), and it's all fetched/processed on the client-side. I'll get around to caching the webmentions myself somewhere at some point...

  • Reply on indieweb.social · 27 April 2022

  • Reply on mastodon.social · 27 April 2022

  • Reply on mstdn.io · 27 April 2022

  • @Hyolobrika Ah the joys of posting that you've done something, then continuing to fiddle with it! By default webmention.io was returning just the latest 20 responses. Looks like I need to implement pagination properly. For now I've increase the responses limit. Cheers!

  • Reply on mstdn.io · 27 April 2022

  • @Hyolobrika Yes and no. Services such as brid.gy are essential to get webmentions from platforms that don't fully implement microformats such as Twitter, Reddit, etc. Webmention.io is a pretty handy go-between to store webmentions as I'm currently serving a static Jekyll site. I've got plans to eventually spin up my own endpoint and cache on a server somewhere, but not enough hours in the day 😭

  • Reply on mstdn.io · 27 April 2022

  • Reply on fedi.pimoore.ca · 27 April 2022

  • WG

    Zomg Max, congrats! Next step: getting rid of third-party reliabilities to send/receive the mentions yourself, perhaps?

  • SS

    My method to implement Indieweb principles and add webmentions support to my Jekyll site is probably the laziest of all. It enabled a decentralized reply system, as well as allowing reposts and likes.

  • Testing

Join the conversation

Reply from your own site with a Webmention (how?).

Webmentions last fetched 15 November 2026, 16:57