Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation
This multi-photo update to @withknown sure makes it easier to quit instagram!
https:/
Thanks @mapkyca @benwerd ;) and gang!
#deletefacebook
Support for importing syndication links for Mastodon Autopost · Issue #75 · dshanske/syndication-links https:/
Now that SL has the Mastodon icon (#66), I'll also note that the latest version of [Mastodon Autopost plugin](https:/
see also: https:/
> The 2.0 update shipping tomorrow attaches a new key to the post metadata: "mastodonAutopostLastSuccessfullPostURL"
> This key contains the url of the last toot.
I've finally gotten around to installing the update for the Twitter plugin for @WithKnown to support the longer 280 character limit. With any luck this will serve as a positive test that everything is working properly.
Have you updated yet?
https:/
Last update turned off checkins in Post Kinds metabox · Issue #34 · dshanske/simple-location https:/
It may have been something else, though I haven't changed anything else substantively recently...
When I updated simple locations with the new release, I think it disabled the visibility for checkins with Post Kinds Plugin. IIRC, there was a check that one did to see if the other was installed and enabled them. Perhaps changes in Post Kinds and Simple Location haven't kept abreast with each other as I believe the on/off in the Post Kinds plugin also moved a version or two back as well.
I want to say that I'd been manually changing the code for a while to show checkins within the metabox, though perhaps after the refactoring of Post Kinds a few months back, perhaps I hadn't and so it was updating Simple Location that turned it off yesterday. I can't be 100% sure, and the number of people using the two in tandem is surely small, so I thought I'd mention it.
In the meanwhile, (as a reminder to myself) I've manually hard coded checkins back on.
Mobile UI suggestion: Chat bubble or menu option to create post from home screen · Issue #24 · microdotblog/issues https:/
The Timeline, Mentions, and Favorites all have a "chat" icon in the upper right to allow one to create a status update. Why not also include this on the main homescreen (or a "Create Post" button just above Timeline) so there's one less step to posting? It also makes it easier for new users to figure out how to post.
Duplication of links upon update · Issue #45 · dshanske/syndication-links https:/
With v3.1.1 and relying on SNAP for POSSE, I'm noticing that after publishing and syndicating, if one comes back and edits a post and then updates it, Syndication Links regrabs the URL's and duplicates the links.
The first unedited version that is shown seems to be a plain http link and after editing/updating, the second duplicated link that is added automatically is an https version.
Manually deleting either of the included links from the Syndication Links box doesn't get rid of the links.
This duplication of the links only happens on posts which have been later edited/updated.
example: http:/
Here the Twitter and Facebook links, which are generated from SNAP, are duplicated, first as http and then again as https. As a test, the two other syndication links are non-SNAP generated links: huffduffer was manually inserted, and the WordPress one was generated from the WordPress Cross Post plugin, so I'm guessing it's an issue caused by the storage of SNAP links (which are https) versus Syndications Links' storage.
New update causes tab issues with All in One SEO Pack · Issue #70 · TweetPressFr/jm-twitter-cards https:/
With the recent update to stable on WordPress.org 5 hours ago (v7.7) a change somewhere in the code is causing problems in the admin interface with the All in One SEO Pack.
In particular one can't switch between the two tabs in AIOSP interface "Main Settings" and "Social Settings". Only the details on the "Main Settings" tab can be seen and attempting to switch to "Social Settings" only changes the url (which then ends with <code>&action=edit#aioseop_opengraph_settings</code>. Attempting to switch back does nothing but change the URL to <code>&action=edit#aiosp</code>.
Disabling JM Twitter Cards and refreshing the post admin interface allows AIOSP to work properly and reenabling JMTC causes it to break again.
Thoughts?
Crossposted to https:/
Update of JM Twitter Cards causes tab issues with All in One SEO Pack · Issue #736 · semperfiwebdesign/all-in-one-seo-pack https:/
With the recent update to JM Twitter Cards to stable on WordPress.org 5 hours ago (v7.7) a change somewhere in the code is causing problems in the admin interface with the All in One SEO Pack.
In particular one can't switch between the two tabs in AIOSP interface "Main Settings" and "Social Settings". Only the details on the "Main Settings" tab can be seen and attempting to switch to "Social Settings" only changes the url (which then ends with <code>&action=edit#aioseop_opengraph_settings</code>. Attempting to switch back does nothing but change the URL to <code>&action=edit#aiosp</code>.
Disabling JM Twitter Cards and refreshing the post admin interface allows AIOSP to work properly and reenabling JMTC causes it to break again.
Thoughts?
Also cross-posting to JMTC which may be the source of the problem.
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:/
![duration](https:/
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:/
Dr. Miller has announced the text for Introduction to Complex Analysis @uclaextension http:/
MIT's self-disruption: an update - Changing Higher Education http:/
Question on @Quora: Is there a simple way to find the permalink URL for a LinkedIn status update? http:/
@ComplexExplorer I try to update it a few times a year... it's nice to be able to subscribe to everyone all at once.