Feature request: Archive internal page/post links to Internet Archive on publish/update 路 Issue #23 路 ManageWP/broken-link-checker https:/
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:/
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:/
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.
Importer "chokes" on Turkey emoji 路 Issue #27 路 jtsternberg/DsgnWrks-Instagram-Importer https:/
I had recently posted the following to instagram: https:/
When the importer came to suck in the data and import it into my WordPress install it resulted in the following error:
![error](https:/
I tried uninstalling, reinstalling, and re-authenticating to see if that was the problem with no luck. I was about to give up the whole affair in utter despair (because DsgnWrks Instagram Importer is my absolutely favorite plugin in of all time and because I didn't want to use Instagram anymore if I couldn't "own" my own photos.)
In desperation, I manually "imported" the post/photo and between that and surprisingly seeing a newer post being imported properly this morning, I'm able to take a reasonable guess as to what the problem is! I also tested on another instagram account and found the same results which "confirms" the issue.
Apparently Instagram posts with the Turkey Emoji 馃 (I'm using an Android phone ) don't work well with either the Importer or even WordPress itself. I suspect that WordPress is viewing the translated code for the Turkey emoji (see also: http:/
Does anyone have any experience in properly sanitizing emoji code to prevent this type of error in the future? Has anyone noticed other emoji that cause problems? I somewhat often use them and haven't seen any issues with other emoji like this.
The quickest fix is potentially to scrub out any Turkey emoji codes in future posts prior to attempting import--particularly as WordPress doesn't seem to be able to handle it properly either.
UI: Duration doesn't make sense in Read post kind 路 Issue #65 路 dshanske/indieweb-post-kinds https:/
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:/
Stylable CSS classes 路 Issue #60 路 dshanske/indieweb-post-kinds https:/
Is it me being crazy, or are all the classes on the data here just semantic?
For front end developers, it would be nice if you included some plugin-wide classes (or ids) to allow easier styling of individual post kinds, particularly since we all know styling on microformats is a bad idea... ;)
Maybe pk-like, pk-bookmark, etc. for the "titles" and a class on the blockquote as well? It seems odd to me that the title is smaller than my default blockquote font, but there isn't anything non-semantic to style on...
UX: Bridgy to Twitter makes some unfortunate default photo choices 路 Issue #691 路 snarfed/bridgy https:/
I'm using WordPress and https:/
Crossposted from https:/
> Surely I should have put in a featured image, but otherwise it's grabbing multiple low res photos on the same page (in widgets, footer, or from gravatar author block) which don't correspond well with the content :
> ?
Ten Simple Rules for Taking Advantage of Git and GitHub http:/
Congrats @raamdev for supporting microformats2 & better #IndieWeb comments in @WordPress Independent Publisher theme https:/
More journalists & newspapers should have open data/code for their stories and interactives like @fivethirtyeight https:/
Thanks guys. I'd managed to brick my computer, and am finally somewhat back up and running. I did have semantic-linkbacks running, albeit apparently with a bug of some sort somewhere. I've run a few tests in the past few days, and things seem to be operating normally now. I'm still unsure of what the bug was, but glad that things seem to be operating properly now. #GitHub #IndieWeb
I like what you've done with the final product and have always thought about doing something similar myself, particularly after I saw what Martin Fenner (https:/
Another thing I've been playing around with lately has been some tools/toys at http:/
A large part of their philosophy is to own one's own data and then syndicate it out to other social media/external site, but some of their infrastructure allows one to easily make posts on one's own page which then act as replies on another's site. This is particularly interesting from the viewpoint of teaching wherein students and professors can interact with each other, but still have/own all of their individual work. (Incidentally, it also makes for using one's own site as a commonplace book of sorts, which I often find valuable.)
As an exmple, you'll notice on the post on my blog http:/
Just noticed via @benborges_ that @dshanske has a semantic markup plugin for @WordPress under way! https:/
Thanks! I'd meant to drop a note into GitHub as well, but given the growth that IndieWeb plugins have been experiencing over the past several months, I thought it worthwhile to encourage some more public-facing attention here.