How I've implemented and interact with the IndieWeb.

IndieWebCamp logo

My Setup

I author posts of various types on this website, some of which I syndicate to silos around the web.

PESOS the description to Twitter and Mastodon then to this website.
PESOS the content to Twitter and Mastodon then to this website.
PESOS the URL and content to Twitter and Mastodon then to this website.
Ones that I’m especially proud of I will cross-post, manually, to this website.
PESOS the check-in data from Untappd using my project, OwnYourBeer, to this website.
Typically posted only on this website.
Typically posted only on this website.

I still need to do some work to change my syndication model from PESOS to POSSE. At the moment, because my Micropub endpoint doesn’t have the ability to modify an existing post, I first post to Twitter and/or Mastodon and grab the permalinks from the responses which are then pumped into the front matter as syndication targets of the post when it gets posted to GitHub.

Tools Used

To handle incoming webmentions, I use, which takes care of parsing microformats and all sorts of filtering to ensure I’m not printing spam or advertisements on my website.

To syndicate interactions on my content inside silos, I use Bridgy to push those interactions through and onto my website.

Outgoing webmentions are handled for me by Telegraph, which also takes care of microformats parsing and endpoint discovery for each link in my content.

I also take advantage of both Bridgy Fed and Switchboard to interact with federated networks and to make WebSub and ActivityPub work.

Lastly, I use OwnYourBeer to syndicate check-ins from Untappd to my beer category.


As much work as I’ve put into my sections of code, I have to give a massive thanks to a handful of people that helped to make all of this happen, as there’s no way I could have done all this myself.

Jeremy Keith
for Minimum micropub endpoint
Aaron Parecki
for Switchboard, Telegraph, and
Ryan Barrett
for Bridgy and Bridgy Fed
Ru Singh
for Celestial