Chris Aldrich

Feature request: Archive internal page/post links to Internet Archive on publish/update · Issue #23 · ManageWP/broken-link-checker https://github.com/ManageWP/broken-link-checker/issues/23

I might suggest the following functionality could fit in well with the plugin's general purpose, particularly since the Internet Archive recommends the plugin. It could also help to "close the loop" in the plugin's overall functionality for helping to maintain data integrity and working links for WordPress sites on the web.

**Suggested Functionality**
When one initially publishes (or possibly updates) a post/page, it would be awesome if all of the URLs referenced on the page as well as that of the page itself were pinged for archiving to the Internet Archive's Wayback Machine at the day and time of their being referenced in the post. (Or perhaps within a day or two of the post so as not to overwhelm Archive.org's servers with multiple subsequent updates for typos/tweaks which invariably happen post-publication.)

With this functionality, then in the future, if (when) resources change, move, etc. one could use the primary functionality in Broken Link Checker not only to restore a link to a close or reasonable copy of the original, but restore it to the _same_ day it was originally referenced.

As I'm sure you're all too aware, this can be very handy as the average web page has a lifespan of 100 days or less. I can see this being very useful to not only the general public, but particularly for bloggers, linkbloggers, journalists, and academics.

**Implementation**
To my knowledge, there are no plugins within the WordPress repository that manage this type of functionality as a standalone plugin, though there is the heavily underused [Post Archival in the Internet Archive](https://wordpress.org/plugins/post-archival/) plugin which essentially adds one's individual post/page permalink URL to the Internet Archive as it's published, though it doesn't include the archival of any links (references) within that same post.

I'm sure that Archive.org/The Wayback Machine may provide some additional documentation for implementation, though I suspect the code in the above-referenced pluign is a very good examplar. I also recently came across this snippet: https://indieweb.org/Internet_Archive#Trigger_an_Archive after a recent conference on Saving/Archiving News Sites which may be beneficial as well. It certainly exhibits at least an interest/demand for such a functionality.

I haven't dug into WordPress core, but I'm guessing some of the functionality for parsing URLs within pages/posts for sending Trackbacks/Pingbacks would have a filter or hook for providing all of the URLs in a post/page necessary for such processing and archiving while the_permalink() or get_permalink() gives the last.

Given the popularity of this spectacular plugin, it could also potentially become one of the largest forces for archiving vast swaths of the internet to the Internet Archive, short of WordPress adding such functionality directly into core.

UI: Duration doesn't make sense in Read post kind · Issue #65 · dshanske/indieweb-post-kinds https://github.com/dshanske/indieweb-post-kinds/issues/65

When making a "Read" post in which data exists in the "time" tab for published dt and updated dt, the output displays more like one would anticipate with a music post type (or jam, listen, play, watch, travel) using start/end vocabulary instead and outputting a "Duration".

Duration may make sense if one were doing a start/end time for their reading, but then the scraper shouldn't be automatically pulling in the publish/update dates/times. Personally I'd prefer to let the publication time of my post indicate when the thing was read and have Post Kinds indicate the publication of the original piece I was reading.

Possibly better would be an if/then statement to differentiate types and for Read types outputting a date/time for the original publication and/or potentially an updated date/time if it exists.

At present, the issue is most common on New York Times posts for which the scraper pulls in the correct metadata.

Example: http://boffosocko.com/2016/11/14/chris-aldrich-is-reading-facebook-restores-iconic-vietnam-war-photo-it-censored-for-nudity/
![duration](https://cloud.githubusercontent.com/assets/5882943/20466247/6e5f67aa-af24-11e6-9d57-f83c3928163f.PNG)

For a small portion of IndieWeb sites, the scraper is returning data in these fields that are identical for both the published and updated fields which returns an odd duration result as well. (See: http://boffosocko.com/2016/11/11/chris-aldrich-is-reading-fragmentions-for-poets/) Perhaps if the date/time in both fields are identical, there could be some error checking to prevent a spurious output since published shouldn't equal updated.