Kicks Condor

LEECHING AND LINKING IN THE HYPERTEXT KINGDOM

I FIRST DISCOVERED
THE 【TECHS-MECHS】WHO
ARE A CLAN OF SOUTH
OF THE BORDER GUNDAM
BREAKING DOWN
IMMIGRATION FENCES
WITH THEIR
IMPRESSIVE MANOS
MECANICAS

PLUNDER THE ARCHIVES

This page is also on dat.

Reply: Webmentions Agnostic

Eddie Hinkle

Well the good news is because Webmention is data agnostic, while I agree microformats can be tricky, if a better solution pops up in the real world, we can easily shift to adopt it. As you said, we shouldnt go out and “try to invent a new spec” but if something makes sense and people try it out and it works, then webmention can always adjust. The webmention spec would never need to change, websites would just have to replace mf2 parsers with whatever the new parsing strategy is.

In a way, Webmention doesn’t even seem like a spec—for crying out loud, it is just source ➡️ target ➡️ endpoint! So, really, microformats are the substance of Webmentions. I think it would be interesting to see a variation of Webmention which did JSON, perhaps using Activity Streams or something. I almost wonder if this is what Parecki is doing by offering three different forms of JSON on all of his posts.

It’ll be hard to beat Microformats, though, in that having a single definitive HTML source is amazing—compared to having all of these other source documents floating around: feeds, ActivityPub outboxes and such. So I’m content to stay put. I already get plenty of great stuff out of Webmentions. Like this ping from you, Eddie!

  1. Haha, yeah you’re right. Source and Target aren’t much of a spec. I think some of the stuff that makes it cross over the line as a spec is “how do you discover someone’s webmention endpoint?”, “how do you verify a webmention’s authenticity?”, etc.

This post accepts webmentions. Do you have the URL to your post?

You may also leave an anonymous comment. All comments are moderated.