Reply to Curtis McHale and David Wolfpaw on rel-alternate

Replied to a tweet by DΛVID V3.0.6DΛVID V3.0.6 (Twitter)
The conversation started in the IndieWeb Chat last week with:
15:27 aaronpk: “my post permalinks now have a rel=alternate link to an mf2 and jf2 JSON version of the post”

And continued over the next several hours and days primarily with participation of aaronpk, GWG, and pfefferle among a few others.

David Shanske (GWG) and I discussed an overview of it in the most recent episode of An IndieWeb Podcast. The conversation about rel=”alternate” begins at the 11:00 minute mark.

Somewhere there’s a note that GWG has already built a big chunk of code into the Webmention/Semantic Linkbacks plugin that implements a large chunk of the work already. There’s also some work done in https://github.com/indieweb/wordpress-mf2-feed as well.

Published by

Chris Aldrich

I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, IndieWeb, theoretical mathematics, and big history. I'm also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.

2 thoughts on “Reply to Curtis McHale and David Wolfpaw on rel-alternate”

  1. GWG has not explicitly build in a chunk of code into the Webmention/Semantic-Linkbacks plugins, the charming part of rel-alternate is, that it works nearly the same way, as the current implementations are working… it simply saves us the parsing part.

Likes

Leave a Reply

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

To respond to a post on this site using your own website, create your post making sure to include the (target) URL/permalink for my post in your response. Then enter the URL/permalink of your response in the (source) box and click the 'Ping me' button. Your response will appear (possibly after moderation) on my page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)