Annotated Transclusion by Aquiles CarattinoAquiles Carattino (aquiles.me)
Should transclusion work both ways, embedding content and letting the source know that I did so? 
If one is worried about link rot for transclusion, why not just have a blockquote of the original in excerpt form along with a reference link to the original. Then you’ve got a permanent copy of the original and the link can send a webmention to it as a means of notification?

If the original quoted page changes, it could potentially send a webmention (technically a salmention in function) to all the pages that had previously mentioned it to create updates.

Automatic transclusion can also be more problematic in terms of original useful data being used as a vector of spam, graffiti, or other abuses.

As an example, I can “transclude” a portion of your page onto my own website as a reply context for my comment and syndicate a copy to Hypothes.is. If you’ve got Webmentions on your site, you’ll get a notification.

For several years now I’ve been considering why digital gardens/zettelkasten/commonplace books don’t implement webmention as a means of creating backlinks between wikis as a means of sites having conversations?

Note: I’ve also gone in and annotated a copy of Maggie Appleton’s article with some additional thoughts that Aquiles Carattino and others may appreciate.

An Indieweb Podcast: Episode 7 The Reverse Salmention

Episode 7: The Reverse Salmention

Running time: 1h 35m 20s | Download (28.7 MB) | Subscribe by RSS

In this last episode before David Shanske and I head to the Indieweb Summit in Portland, Oregon, we discuss updates to people’s Indieweb experience, little things David has hidden in plugins, web-signin vs IndieAuth, etc.

We’re both looking forward to seeing those of you who can join us in Portland.

 

Huffduff this Episode