Skip to main content

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






Support for importing syndication links for Mastodon Autopost · Issue #75 · dshanske/syndication-links

Now that SL has the Mastodon icon (#66), I'll also note that the latest version of [Mastodon Autopost plugin]( should now also support importing the URL for the last successful toot to allow the closure of automating the POSSE loop.

see also:
> The 2.0 update shipping tomorrow attaches a new key to the post metadata: "mastodonAutopostLastSuccessfullPostURL"
> This key contains the url of the last toot.


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

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.


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: 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.


Stylable CSS classes · Issue #60 · dshanske/indieweb-post-kinds

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...

![css classes](


UX: Bridgy to Twitter makes some unfortunate default photo choices · Issue #691 · snarfed/bridgy

I'm using WordPress and in my workflow. I like that allows for up to 4 photos and how they're laid out, but we (WordPress users) may need some additional control over what photos are chosen by default...

Crossposted from as well.

> 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 :
> ![bridgy publish](
> Maybe default to none if not a featured image or appearing within the_content()?


Replied to a post on :

Webmentions failing sporadically · Issue #682 · snarfed/bridgy

Sometime in the last week I find I'm sporadically missing webmentions from both Twitter and Facebook. It doesn't happen all the time, but I feel like I'm missing about a quarter or so of what should be coming back.

I've tried resending them through the UI and it seems they then make it about 50% of the time.

The responses I'm seeing on those that fail are similar to the text below

> 2016-07-11 09:48:49.613280 I Giving up this target. {'body_json': {u'error': u'Could not find account for Is it registered with Bridgy?'}, 'code': '...', 'request': u'POST (with source=, target=', 'http_status': 400}

This appears to me to be that thinks I have a WordPress.**COM** account rather than a self-hosted .**ORG** version. I'm unsure what could be causing this and don't seem to find any type of commonality for why some fail while others go through.


Replied to a post on :

About/FAQ missing reference to webmention-endpoint? · Issue #673 · snarfed/bridgy

I'm always a fan of instructions being built intuitively into the UI flow, to guide new users along, especially if they have a solid idea of what they're getting into in the first place. In this particular instance, the reference to the HTML was a tad too nebulous and may confuse many -- especially those who begin reading rather than jumping right in.

Shortly the indieweb will be so big that totally tyro users with no facility with code will be on the doorstep and will need better explanations/instructions. Perhaps I'll take some time in the coming months to put together simple walk thrus for the handful of major platforms? If you think it's worthwhile, can you let me know, based on the current userbase (or even recent growth in the past 6months-year), how you'd rank them in order of priority so we can help the biggest groups first? Or perhaps it's worth starting at the lowest hurdle for the least technical users (Tumblr/Blogger?) and building toward the more technical ( (I'd presume most above this level are okay with most of what exists now).

I'm presuming that was originally meant as a "code" bridge to connect activity on silos, but I can also see it as taking on a secondary meaning in providing the initial value and impetus to bridge users into to the bigger IndieWeb movement.


Replied to a post on :

About/FAQ missing reference to webmention-endpoint? · Issue #673 · snarfed/bridgy

In the FAQ there's a line about "Why do I have to add that line of HTML to my blog?"

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="" rel="webmention" /> or on WordPress
<a rel="webmention" href=""></a>

I think the 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.


Replied to a post on :

rel-feed support for Bridgy and Instagram #40
While I'm thinking about Bridgy/Instagram support and mf2, I thought I'd cross post this issue snarfed/bridgy#671 (comment) here as it doesn't look like SemPress supports this out of the box.


Replied to a post on :

Not receiving webmentions via Instagram on #671

I notice I'm not receiving likes/comments from Instagram via Bridgy (and apparently never have.)

I'm using OwnYourGram to PESOS Instagram photos into a WordPress (.org) site, which are then marked has having been syndicated using the Syndication Links WP plugin. The Instagram post naturally doesn't have a link to my web site's post, but my sites's post does have rel-syndication and u-syndication like so: `<a title="Instagram" class="u-syndication" href="" rel="syndication"> </a>`

Is there some other smaller fine point I'm missing from the about page and support? Has anyone else seen this with WP (.org)?

Cross reference:
with post "syndicated" from


So yesterday there were 5 hits on this post, while today there were 37. This post is currently ranked #6 on a google search for the string "Chris Aldrich Dating Naked". A Google search on "Chris Aldrich" is substantively the same as the past several months except that the profile page for the "other" Chris on VH1's site is ranked #2, while an article is ranked #8. His twitter account logs in at #15 and the next closest mention is at #69 for an US Magazine article. On Twitter, @ChrisAldrich860 currently has 139 followers.