Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, Indieweb, and the entertainment industry including: finance, distribution, representation
This is just the kind of post I added a chicken feed to my WordPress site for. #pressedconfused #indieweb #fun
https:/
http:/
RSVP invited · Issue #156 · pfefferle/wordpress-semantic-linkbacks https:/
When Brid.gy sends webmentions for people invited via a Facebook POSSE copy, the webmentions for these people don't show up properly in comments because `semantic_linkbacks_type` is set to "invite" instead of "rsvp:invited".
Manually effecting the change in the database provides the expected display. See: http:/
I love the mission of @ScienceSites. Are all your sites based on @SquareSpace or do you build with @WordPress, @Drupal, et al.?
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.
Today's afternoon sessions for IndieWebCamp Baltimore are posted! Links for video feeds coming
Sessions include #offlineposting #micropub #identity #interactivetranscripts #wordpress #prettywebsites #physicalweb #microformats #IoT
https:/
YouTube URL embeds not working · Issue #1 · dshanske/twentysixteen-indieweb https:/
In archive views (/kind/post_kind/) and individual pages, typical raw YouTube URLs in pages that previously converted them into embeds via WordPress now just display them as text (non-clickable) URLs.
This may also extend to other types of WordPress embeds as well.
Makes me wish I was in Auckland at the end of the month to chat with @billbennettnz on @WordPress and #Journalism
https:/
Turning Webmentions into comments for native display on #WordPress
#facepile #IndieWeb
http:/
Anyone want to join me for an impromptu BoF/hallway session on #IndieWeb technologies with @WordPress at #WCLAX this weekend? #ownyourdata
#40031 (Consider Adding Web Annotations to WordPress) – WordPress Trac https:/
Mostly to provide some additional resources to the conversation I'll add the following:
Web Annotation Working Group's [https:/
Prior to the WPTavern post which motivated the conversation, there was a [https:/
Keep in mind that some of the standard is geared specifically toward browsers and browser vendors, though WordPress could certainly implement some of the pieces from the CMS side.
Old posts with no value set for `pf_forward_to_origin` are automatically forwarded · Issue #899 · PressForward/pressforward https:/
This has probably been present for a while, but I just noticed after turning on forwarding posts to the canonical URL by setting a time >0 in the forward settings: all the old posts in my database (prior to having PressForward) auto forward as a default back to their own URLs. This means that every X seconds (as set in the setting) pages on my site automatically reload (or are redirected to themselves) and this makes the site relatively useless to attempt to read. (This seems to be a follow on error not noticed in https:/
Users adding PressForward on preexisting sites are going to have a tremendous shock if this is the default.
A better option is that all old posts (prior to installation) should default to no-forward (or at least not forward if there is no value set for `pf_forward_to_origin` in the database. PressForward should, in my mind, ideally default to no-forward in all new future posts with the possible exception of posts generated specifically by PressForward's nomination/draft workflow to default to `forward`/`no-forward` based on a possible new setting option in addition to the time setting.
It would be nice if the portion for null/non-existent values of `pf_forward_to_origin` was fixed before 4.2.2 rolled out into the WordPress repository if it hasn't been pushed already.
Running 4.2.2 on WP 4.7.2
Congratulations again to everyone, as always, on what I think is surely one of the most valuable plug-ins in the entire WordPress repository.
OPML link not working · Issue #898 · PressForward/pressforward https:/
## What I tried/expected:
From the page `/wp-admin/admin.php?page=pf-tools` under the `OPML Link` tab, the instructions indicate:
You can share your subscription list as an OPML file by linking people to http:/
## What happened:
Visiting the indicated link throws the following error:
`Warning: Creating default object from empty value in /htdocs/example/wp-content/plugins/pressforward-4.2.2/includes/opml/object.php on line 48
1`
## Additional information:
I've got a handful of feeds, so I should expect something to appear. Is there a setting I'm missing somewhere? I know that there's a setting for the /feedforward RSS functionality/plugin, is there a similar one for OPML that I'm missing?
Running GitHub version 4.2.2, WordPress 4.7.2
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.
Retrieve Running Time for listen and watch post kinds? · Issue #71 · dshanske/indieweb-post-kinds https:/
For sites like Soundcloud, ITunes, Netflix, youtube (if it's available) it would be nice to retrieve the "running time" of the music, show, film, etc. to display as a running time in the UI for listen, watch, and jam types (rather than the published/updated) for other post types.
Sample URLs
https:/
https:/
https:/
https:/
https:/
WordPress blueberry podcasts: http:/
When not scrape-able, allowing one to simply enter a 0:00:00 time and a finish time and letting it display the appropriate running time (without entering a date) would be useful for these types as well. (I'm presuming it requires dates to calculate currently as I haven't yet checked....)
Suggestion: Store GPS coordinates in the recommended WordPress format/standard · Issue #29 · jtsternberg/DsgnWrks-Instagram-Importer https:/
It would be nice if the plugin stored the GPS coordinates with the standard/suggested WordPress standard:
https:/
This would allow the usage of secondary plugins (like [Simple Location](https:/