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.
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:/
Update: Twitter List for #DtMH2016 went from about 30 just before the conference to 158 just two weeks later. http:/
Dr. Miller has announced the text for Introduction to Complex Analysis @uclaextension http:/
Sounds like a reasonable solution. I'd imagine that in most cases (to be safe) that if there's not a featured image, then posts to twitter would generally be just the text update as that's how most people typically use twitter.
Is it looking for photo related microformats with regard to identifying/pulling photos? I actually thought it was interesting/relatively nice that it automatically pulled the three photos and laid them out that way, but in that case I'd have done higher res photos for better clarity. The "indieweb mini-logo" is a really small icon way down in the footer of my page and I was most shocked that it popped up on the post.
I typically have been using SNAP for POSSE, but as I've been watching your work recently, I felt compelled to test out Bridgy Publish to give you some feedback about UX/UI as well as bang on things for bugs in general.
Mitch, I also love SNAP! If you didn't see it, they added Medium support in their last update after Medium released their write API. Medium also has their own WordPress plugin which will allow you to broadcast there easily and quickly too.
if you're game, there's a few other tools you might think about adding to your workflow:
First you should know about http:/
One particular one that integrates well with SNAP is Syndication Links [https:/
I can now update Tumblr from my Known Account!
[Edit: At least I thought I could, but something is apparently amiss...]
Cannot redeclare class RelMe_Widget · Issue #36 · indieweb/wordpress-indieweb https:/
Just updated to the newest IndieWeb plugin and got:
Fatal error: Cannot redeclare class RelMe_Widget in /wp-content/plugins/indieweb/includes/class-relme-widget.php on line 87
I hadn't gotten a chance to do the update to Syndication Links yet. Could that be related? Do they both need to be updated simultaneously?
About/FAQ missing reference to webmention-endpoint? · Issue #673 · snarfed/bridgy
In the FAQ https:/
Am I now missing it or did the actual line of HTML that's being referred to disappear from the page in an update?
I'm presuming it's referring to:
<link href="http://yourwebsite.host/webmention-endpoint" rel="webmention" /> or on WordPress
<a rel="webmention" href="https://www.brid.gy/webmention/wordpress"></a>
I think the brid.gy interface prompts the user to include such a line when signing up for service, but it may also make sense to mention it on this page in this section somewhere for completeness? It could certainly be referenced here for those reading the "about" page prior to actually attempting to set things up.
As it's not in the WordPress directory, it won't matter too much. For those who do try it out however, the existing one that is in the WP directory has a higher version number and so WP will automatically prompt them to update it. The unsuspecting novices who aren't paying attention will likely blindly update and thereby completely override the plugin with a separate piece of code and functionality. Something to be aware of from a UX perspective if you hadn't noticed. #CaveatEmptor
I've noticed in many places on http:/
How to find/create a URL to a status update post on LinkedIn
In addition to the manual method mentioned by Brannigan (on 7/14/15) [http:/
The two "stem" URL formats are as follows:
https:/
https:/
Where the XXXXX indicates the topic ID number that is unique to each post.
To get this ID number:
* Find the post (either natively or on their own page by using the menubar: Profile / My Updates).
* Then highlight the word "share" in the bottom of the post and right click "Inspect" (in Chrome, though other browsers allow means of viewing source code/CSS for pages as well, see also firebug for Firefox).
* The topic ID will appear just below the <span> for the share button in the <form class="comment-box"> tag.
* Take the topic ID number and replace the XXXXX with it at the end of one of the two stem URL's above and you've now got a direct URL for your particular status update.
Example: https:/
Naturally, it would be far better if LinkedIn would just wrap a direct anchor tag around one of the post elements so it could be more easily cut and pasted when necessary. (Facebook, Twitter, Google+, and most other social media networks do this or even provide embed code to make it easier.)
I'll also note for those with programming skills that LinkedIn provides at least limited API access for posting updates and returning the resulting URL. The opensource Known platform uses it and there's a plugin available on Github with sample code for those who might appreciate it: https:/
@dshanske as you update Post Kinds, particularly "read" type, you should be aware of @kylewmahan work with @goodreads @kevinmarks
Cross reference: https:/
@kevinmarks @kylewmahan I also imagine that status updates for @goodreads also have two different and mutually exclusive data indicators for progress: one by page (for physical/printed books) and one by percentage (%) for ebooks which don't have 1 to 1 mappings for pages. The final field is likely a text one with a max of 420 characters. I also image that they have fields for indicating crossposting the status update to Facebook/Twitter which are done separately in their backend settings. Twitter is done in the back end settings as a default if permission is given while they actually have a checkbox for crossposting to Facebook. (I'm not sure why they have this odd difference in the UI)