Replied to a thread by Scott JensonScott Jenson (Twitter)
Aaron’s site is so advanced, his replies on Twitter don’t have a permalink back to his site. So you’re missing out on the way he replies and collects replies/likes/reposts. See: https://aaronparecki.com/2020/12/10/7/

Mine is less so; you’ll see my permalink on Twitter back to my original.

It doesn’t look like he threads his entire conversations (publicly), but you can currently see the contexts and replies from your conversations at https://aaronparecki.com/replies.

screencapture of Aaron Parecki's site capturing conversation back and forth with Twitter

A difference you’ll notice is that Twitter caps me at 280 characters, while I can waffle on for days and Aaron’s website will likely (but doesn’t have to) capture it.

Webmention also allows for editing/sending updates, so I can edit after-the-fact and Aaron’s site will show it whereas Twitter doesn’t allow edits, so… I could also delete my response in the future and send a “410 webmention” and Aaron’s site should delete it.

I’m sure that Twitter, Facebook, and most other social media systems could implement sending/receiving webmentions in under a week (even if they’re dragging their feet on a well written spec) and add microformats to make cross-site notifications and comments a reality. It will assuredly require legislation for them to do so however.

Many common CMSes already support Webmention either natively or with plugins/modules, so there’s some pretty solid proof of interoperability with various software and programming languages.

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.

One thought on “”

Leave a Reply

Your email address will not be published.