Skip to main content

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







@devilgate I'd noticed that too... Perhaps report the bug here:


.@WordPress is supposed to be democratizing the web, and this sounds like anything but


I'm sure I've used this same signal sub-consciously in the past. Fortunately most spammers don't bother to add avatars of any stripe. Although I've also found that even many actual legitimate commenters (and specifically WordPress users) don't know about or don't have a gravatar account either. Better yet, I've turned off traditional comments in the past in preference for webmentions, for which I've yet to see any native spam yet. The majority of people using this method seem to take their identity a bit more seriously which also raises the signal-to-noise threshold.


@macleodan iirc, @jimmymansaray had same question last year. I know he looked at both @WordPress & @withknown.


I suspect that markdown or semi-complicated html (like you, I occasionally like to do this too, even if it's just bold or italics) in replies are a second class citizen because most major CMSes (including Known) strip out or severely limit (for security reasons) the html that is accepted in comment fields. In fact, to conserve on space, I've even noticed that many even strip out blank lines between paragraphs! Many also will mark as spam comments that have one or more URLs in them. As a result doing fancy or even mildly complicated html or markdown in replies is something for which most platforms just don't build.

The other issue in status updates and replies is that they're often syndicated to other platforms and it's a more difficult issue to properly do this with each snowflake social media silo depending on how they individually handle html/markdown (or not). I do this sometimes in WordPress to properly format syndicated content, and it easily triples the amount of manual work, so be careful what you wish for. (This may also be the reason I love Known so much too!)

Every now and then I'll write an extended reply to someone's post that gets to the point that headings, additional structure, and the frills become much more valuable. In those cases, I'd probably then default to make them posts/articles and add the additional touches and then do a manual mark up of u-in-reply-to to have them show up as a reply instead of just a mention. This happens so generally rarely that it's not too much of a headache.

Either way, the end result on the other person's site isn't something I can ever control for, so I try not to sweat it too much. :)


For the syndicated portfolio, you might want to take a peek at the PressForward plugin for WordPress []. While it is a stand-alone feed reader under the hood and could be used for creating an editorial flow, it will let you use a simple bookmarklet on your work published on another site to make a quick and complete copy of the post on your own site. Within the plugin settings you can set a "time to forward" (I use one second) such that people who visit that particular post will be automatically forwarded to the original (and canonical URL) on the commissioning outlet's site.

As an example, compare: (which is a bookmark with some commentary pointing to my post)
to (which is an exact copy of my post, which only I can see on my backend, that redirects the viewer to the original on AltPlatform).

This is beneficial as you can syndicate (POSSE) the post with your own URL to Facebook, Twitter, et al. and folks who click to read will be sent to your site for a moment before being forwarded on to the original. Thus you get a ping and the original outlet also gets a ping (as well as the advertising revenue for it.) And if, for any reason, the original outlet goes out of business, gets sold, or disappears, you've got a word-for-word copy of your original and can simply un-forward it so that it can appear on your site as it was originally published. Naturally if you prefer and the outlet doesn't stipulate otherwise, you could publish the original to your site and not forward it (or even forward it for an exclusivity window of time pre-agreed with the original publisher.)

Additionally, if you're using for backfeed, anyone who comments on your POSSE copies will have their commentary sent to your site. While others won't necessarily be able to see the commentary (if you're forwarding the URL to the publisher's original), at least you'll be aware of it and can reply to it and get your own replies in return. I suspect that in the future may be able to scrape commentary based on the syndicated URL so that your personal version aggregates commentary from the publisher's original as well as mentions of it on Facebook, Twitter, et al.

There are still some missing pieces I'd like to see in such a workflow for journalists, but it's slowly and surely getting somewhere.

(I've written about other parts of PressForward before at as I also have an off-label use-case to replace read it later apps like Pocket and InstaPaper.)


@billbennettnz You might also find the Indieweb-WordPress chat room useful while you build:


@billbennettnz Indieweb Press This plugin will also give you a bookmark for marking up "likes" pretty quickly too


@billbennettnz I'm using the Post Kinds plugin which covers many types including "likes":


Replied to a post on :

Perhaps related to this?
Particularly with instagram involved? I don't see a link to his feed and his feed (/blog/) isn't on his front page, so bridgy may not be finding it for that reason.


Jeffrey, I came across your site while looking for some opensource OPML tech (thanks for the plugin by the way) and ran across this post on Wallabag. I too had a similar problem/use case and wanted to get out of Pocket so I could better own my data. I ran across the PressForward WP plugin which does a lot of fun stuff towards this end. I've written up some thoughts about it when I did it. You might find them useful if you haven't settled on a solution for yourself.


The duplication of Instagram posts was a bug that got fixed. Mostly it's got a bunch more post kinds (you can choose which in the settings) for those who want them, though if likes and replies are all you need... Hopefully you've found the IW Press This bookmarklets to make things easier:

Some people find that they prefer to tweak the CSS for the display of the kinds and David Shanske is also building in some customize-able templates to make things easier for those who want to tweak things for better display.


Replied to a post on :

A few days ago, in part based on something that [Richard MacManus wrote]( (and which may have prompted @scripting's response), I noticed that Inoreader differentiates between importing an OPML and subscribing to an OPML.

> # Importing an OPML
> If you import an OPML file in your RSS reader, you are creating a static copy of the reading list. If the owner of the original list updates the list, this change will not be shown in your feed collection.
> # Subscribing to an OPML
> An OPML subscription, however, creates a live connection between the original source and your feed folder. Whenever a feed is added or deleted from the original list, the change will be reflected in your subscriptions. The notification system in Inoreader will notify you that new feeds were imported or existing feeds were removed.

Ideally, if a site had a blogroll or other mechanism by which they maintained and publicly published their own OPML list, then the user could plug that into the reader to subscribe to the list which could update dynamically. One could also subscribe to others' OPML lists (or subsets of them?) as well without needing to pay attention to them. In total, this sounds like what Ben's reader (and Known's subscription list) were doing, but by using a pre-existing standard that's broadly supported. (As an example WordPress sites with the Links module enabled publish their OPML files at