Skip to main content

Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation






@vv4rner While I love what RSS enables and there's a huge ecosystem for it, I am against it for DRY reasons. It's stable in the fact that no one has iterated on it in over a decade. It also helps that WordPress core handles a lot of the admin tax for me on maintaining it, but it has caused metacrap issues for me in the past.

So what to do to replace RSS? If you look at most of my content, I've got the HTML marked up with (richer) microformats for those who'd like to consume that directly without needing a side file for it. There's an existing ecosystem of microformats parsers and even social readers that use microformats over RSS. Incidentally microformats are also part of the semantic layer that makes site-to-site converstions on IndieWeb-based sites work better.


@sillygwailo Until there are consuming use cases for it, it's not relevant, but basic text with `h-product` and a `dt-published` for first dose datetime and `dt-updated` for subsequent boosters might make sense based on existing work? See:


@DavidWolfpaw @curtismchale @EricMann Have you followed some of the recent discussion around rel="alternate" to get around the issue of proper use of microformats in WordPress core and/or themes? This could really accelerate the uptake for a great many.


@jgmac1106 If you're as poor a theme tinkerer as I am but about to embark on adding microformats to a theme, I might recommend taking a look at the individual commit changes that David Shanske goes through in converting the base Twenty Sixteen Theme into a more IndieWeb friendly theme. The list of commits with useful labels can be found here: Clicking on each of the changes will give you highlighted changes for what he did.

I would recommend starting at the bottom and then slowly reading your way to the top to try to understand what he's doing in each section. Note that there are one or two places where he splits a particular change up between a few commits or occasionally backtracks. There's also a section in which he "rips" out the WP core functionality of Post Formats in favor of using the Post Kinds Plugin--I'd recommend you don't do this to make your resultant theme the most flexible. I believe there's also a section in which he adds a "comment walker" and later removes it because the experimentaly functionality was later merged into the Webmentions/Semantic Linkbacks plugin to better handle comments, so you can safely ignore may of those chunks which are now stable.

I suspect that between this and the code models for SemPress and Independent Publisher (which should also have some David Shanske specific commits and related discussion that you can look up) you may be somewhat better off.

Good luck! We're all cheering for you!


@mattmaldre I suspect it won't change much, since they're primarily used/displayed in comment sections. The bigger effect is going to be on products like Post Kinds Plugin, which may (hopefully) provide even easier modularization for injecting microformats into one's site.


@EddieHinkle @jackyalcine @wilkieii Almost as a joke on Facebook functionality a while back, I posted this voting related post:
There are some interesting suggestions and use cases here as well:


@jgmac1106 I've often wondered about potential expanded vocabularies for microformats within the educational space. I know many use a variety of other metadata including schema and dublin core, but I've never really come across any application which consume these or do anything useful for them other than add an administrative tax to the user who are doing them. Perhaps we should begin documenting some of them to build a more long term valuable solution?


@spigot It's not, instead it looks like it's caused by the microformats and their placement in your particular theme.
You can find a preview of what Bridgy will publish at if you want to test before sending.


@huby And now the bigger reveal! Since you've liked my tweet, you'll notice that I'm backfeeding reactions and comments from my tweets, so your "like" also lives on my website at the original post which was syndicated to Twitter.


@huby plain old semantic HTML with microformats in combination with the webmention protocol allow one to post "likes" to one's own website and send them to others. Here's a simple example:


@kaushalmodi Also, on your site I'm seeing rel=me instead of the rel="me" with the proper quotes around me. See for examples.


Replied to a post on :

Within the past month [it's guestimated that over 1 million webmentions]( have been sent on the internet. There's not really solid research on how many sites physically send and/or receive them, but as of [last June]( the conservative number was in the range of about 5,000 and the number is increasing rapidly, particularly with platforms like (5-10,000 accounts) now supporting them out of the box and CMSs like Drupal (via plugin) and Perch having added them since then. This also doesn't take into account an anecdotally sharp uptick of adoption on WordPress via plugin, most notably by several WordPress core developers.

Mastodon already supports most microformats for webmention to be implemented more easily. and

There are already a number of open source tools that might also be bootstrapped for something like this as well:


For those interested in more and who know a bit of code, David's also got a "master class" on adding microformats to modern themes in his commit trail for updating/upgrading the TwentySixteen theme to be more IndieWeb friendly:

While it isn't comprehensive and may not cover every eventuality for every theme, following along with his commits here will get you a long way towards better understanding microformats v2 use with WordPress. I think I've learned more about WordPress themes and microformats by following his changes here than anything else I've tried.


Today's afternoon sessions for IndieWebCamp Baltimore are posted! Links for video feeds coming
Sessions include


I suspect that next, with a tad bit of parsing using microformats, you can add some display elements to your webmentions to indicate the author, their url, date/time, and actually include the reply text to have a better UI for them. Then they'll look a bit more like the traditional comments you may have envisioned. (Something along the lines seen in my comments at There's help to be had in the chat as surely someone has documented this somewhere before and you probably won't have to build from scratch unless you really want to.