you can do something really cool called webmentions where your tweets will basically ping back to your website so you can have all your content forever. i would never do that bc most of my twitter is shitposts but i would love to see if there's something similar for instagram— christina (@_christinadan) October 17, 2020
Using Actionsflow to automate the sending of Webmentions using webmention.app
Perhaps it’s something I might use in conjunction with my work with TiddlyWiki, MediaWiki, or my Obsidian.md notebook projects.
I’m hoping that future versions of this provide the Twitter permalinks for the syndicated copies there to be returned to my WordPress site for storage. In my case, I’m using the simple Syndication Links plugin which has storage and/or finds the storage location in WordPress to allow for the display of those permalinks in my post to indicate where I’ve syndicated the copies. This does two things: it’s a reminder of where my content lives elsewhere on the web (especially if I later want to go back and delete them, or to delete them if I’m deleting or making the original post private/unpublished) and it allows services like Brid.gy to find my original post and backfeed replies to the Twitter versions back into the comments section of my post using the Webmention spec (via the Webmention plugin and the Semantic Linkbacks plugin).
This past week I had the pleasure of being on the Learn with Jason Show to show how to add Webmention functionality to a NextJS website. Webmentions let you pull tweets, other blogs, and other activity from around the web into your site? It was fun live pair programming the implementation of webmentions. Check out the video or read some of the highlights below!
Thirteen: Backfeeding ideas with Brid.gy
Let’s say I syndicate a thought to Twitter. I can use Bri.gy to backfeed ideas and interactions with my Tweet back to my original in my digital notebook (where it’s most useful). This helps outside ideas filter into and interact with my own ideas.
You knew ideas can have sex, right?!!
Twelve: Webmention for backlinks
For my backlinks I’m relying on the W3C recommendation Webmention spec which I’m implementing with the WordPress Webmention plugin. This allows me to cross link my own posts to look like “comments” or “replies”, but it allows others to ping me and interact with my public posts and their syndicated copies.
Need a primer on what webmentions are and what they can be used for? I’ve got you covered:
Webmentions: Enabling Better Communication on the Internet
The nice part is that this sort of model allows the user to collect this data and send these notifications on an as-desired basis to the publisher.
Thursday, October 1, 9:30 - 11:30 AM PDT
Guest: Monica Powell
This episode will air live at twitch.tv/jlengstorf!
Did you know that Webmentions let you pull tweets, other blogs, and other activity from around the web into your site? In this episode, Monica Powell teaches us how to add it to a Next.js site!
I’veif others want to join.
Marty wrote a great, thoughtful essay about some of the problems with webmention right now, and I agree with it.
By that I mean, a sender attempts to send a mention and if there is no endpoint or the send fails, then as a back up, the sender parses the receiving site’s page for an h-card and if an email address exists, sends an email notification there instead?
Might be helpful for those who don’t yet have Webmention set up, but could act as a backup. Then when they have things working later, they could force manual mentions to recollect them? Also useful for those who’d like notifications, but don’t want to build infrastructure or who might not want to show comments on their site either.
Pingbacks are essentially dead and in personal experience some of the few sites that still support them are in academia, but they’re relatively rare and have horrible UI in the best of times. Webmention is a much better evolutionary extension of the pingback idea and have been rapidly growing since before the spec was standardized by the W3C.
I’ve sketched out how individual academics could use their own websites and publish pre-prints and syndicate them to pre-print servers and even to their final publications while still leveraging Webmentions to allow their journal articles, books, other works, to accept and receive webmentions from other web publications as well as social media platforms that reference them.
I think the Microformats process is probably the best standardized way of doing this with classes and basic HTML and there is a robust offering of parsers that work in a variety of programming languages to help get this going. To my mind the pre-existing
h-cite is probably the best route to use along with the well-distributed and oft-used
<cite> tag with authorship details easily fitting into the
As an example, if Zeynep were to cite Tessie, then she could write up her citation in basic HTML with a few microformats and include a link to the original paper (with a rel=”canonical” or copies on pre-print servers or other journal repositories with a rel=”alternate” markup). On publishing a standard Webmention would be sent and verified and Tessie could have the option of displaying the citation on her website in something like a “Citation” section. The Post Type Discovery algorithm is reasonably sophisticated enough that I think a “citation” like this could be included in the parsing so as to help automate the way that these are found and displayed while still providing some flexibility to both ends of the transaction.
Ideally all participants would also support sending salmentions so that the online version of the “officially” published paper, say in Nature, that receives citations would forward any mentions back to the canonical version or the pre-print versions.
Since most of the basic citation data is semantic enough in mark up the receiver with parsing should be able to designate any of the thousands of journal citation formats that they like to display any particular flavor on the receiving website, which may be it’s own interesting sub-problem.
Of course those wishing to use schema.org or JSON-LD could include additional markup for those as well as parsing if they liked.
Perhaps I ought to write a longer journal article with a full outline and diagrams to formalize it and catch some of the potential edge cases.
If you have questions/problems with them or want to chat with the developers on potentially improving them, I’ll invite you to join the IndieWeb WordPress chat: https://chat.indieweb.org/wordpress/.