Previously we have contemplated the need for complementary notice on fork. Here, I start to think through how such a mechanism might work. I draw inspiration from Webmention 
.
While thinking about complementary notice on fork we proposed that the notice should be delayed until the first content change.
_**N.B.** The ideas presented here are very much a series of thoughts in progress._
Unlike Webmention, in the Wiki we have two potential forms of back link that we might want to inform the original site about.
Both of these types of back links provide a mechanism for content authors to make discoveries about the use of their content outside of their current neighbourhoods.
* Where a page is forked and its contents modified, and * Where a forked page is linked to from another page.
Fork History
Who receives a notification, if there are multiple forks in a pages history?
- User Aaron writes a pages on his wiki
- User Brian discovers Aaron's page a forks a copy
- User Carol discovers Aaron's page, on Brian's site and forks a copy of Brian's version of the page.
- Carol edits the page
Question:
Who receives a notification that Carol has modified the page?
Thoughts:
As the original page author I think Aaron should. But, should Brian? Maybe it depends on if Brian has made changes to the page?
Should notifications be private?
Keeping notifications private, at least, in the first instance would seem to be good. Providing a first level of defence against defacing/spam.
Allowing the notification to be made public, can also be good. Allowing other to become aware of the evolving content, even if the original author does not want to fork it back.
Where to report?
Should Wikimentions report back to the site of the page being mentioned, or to single, central, service run by the owner?
Reporting back to the site being mentioned might be simpler. But, providing a user with a aggregated view of the Wikimentions across all their sites would be beneficial.
.
From IndieWeb Summit 2018, posted by Jim Pick [dat://fritter.hashbase.io/thread/dat://c6740b08b319265079ebb9da98ee11a01da5d5379ca5d0ef12fa539403532372/posts/0jizb0zr7.json fritter]
I snipped out @gozala 's show-and-tell from IndieWeb Summit and uploaded it to Hashbase... dat://indieweb-summit-2018.hashbase.io/ind... His demo shows sending a Webmention from inside Beaker Browser! This is what a Webmention is... https://indieweb.org/Webmention To run the demo yourself, load up a test page where you can make a webmention, eg. https://webmention.rocks/test/1 Then go here, and write a comment which will be used as a webmention: dat://d58a4ed2df295e9c994c3f4a6934b3e946ab5e497f65cd2c7ab6adbb26d9ae9f/ You will be prompted to select a Dat from your library or to create a new one to hold the webmention data. Just create a new one with a creative name you will remember ... eg. "webmentions". If all goes well, behind the scenes, the webmention will be saved to dat, and relayed to the test page ... behind-the-scenes, there's a gateway that does that for you, and which also proxies your dat content. If you go back to the page you commented on, you should see your comment! https://webmention.rocks/test/1 The demo uses a Node.js gateway server which lives here... (you shouldn't have to touch it) https://glitch.com/edit/#!/datmention
.