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






I've updated my WithKnown install to v0.9.9 Derbyshire!

2 min read

Aside from one or two custom CSS tweaks, everything seems to be looking and working as expected! If readers or users see or experience any issues, please let me know.

I can't wait to try out all of the new core features and improvements that have arrived since 0.9.2! Including:

  • A simpler user registration experience
  • Fixed image preview rotation
  • Improved indieweb support (including for likes and reposts)
  • Improved migration support
  • Advanced access control internal API
  • Design and layout fixes
  • Better error pages
  • Support for PHP 7
  • Countless fixes and speed improvements in the background

You can get your own version of one of the best, most modern, and most forward-thinking Content Management Systems on the planet by contacting the fantastic team at Or host your own version: with lots of community developed plugins.

If you've already got Known and haven't upgraded, I've previously written up an outline about the upgrade process.

Coming up soon, I'll be upgrading my Known testing ground at which, in some sense, is its own social media site, but also allows users to sign up for an account to test drive some of the core functionality in addition to syndicating their content to sites like Twitter and also backfeed their comments back from Twitter. For ease of use, I recommend setting up the bookmarklet after creating your account.

The 1.0 version of Known is anticipated some time in June 2017, but to be honest, in the almost three years I've been using it, it's been both fantastic and rock solid.


Certainly an interesting and different way to do #annotation of older sources for the web. #IndieWeb

1 min read

<blockquote class="twitter-tweet" data-lang="en"><p lang="en" dir="ltr"><a href="">#Facebook</a> <a href="">@_Four_Horsemen</a>  ...the individual is no longer a person, it’s a commodity: <a href=""></a></p>&mdash; Blake B Wright (@WrightBlakeb) <a href="">October 1, 2015</a></blockquote>

<script async src="//" charset="utf-8"></script>


Thank you for sharing your commonplace book with us @KevinMarks #indieweb

1 min read

I'm always impressed with Kevin Marks' use of his website(s) (kmk) as a commonplace book. It has to be one of the best personal versions of such a construct on the internet today.

Any time I (or others I've seen) have a question, he nearly always responds, "I wrote this last [chose one (or more): month/year/decade]" followed by a link(s) to his site where there is a carefully crafted and well thought out article he's written on the subject. By comparison, others would, if they're kind enough, Google the subject and dump out random answers that may or may not be of any help.

I write all of this in some sense because it inspires me to aspire to such kindness and thought, but mostly to say, "Thank You, Kevin!"


Description and FAQ for IndieWeb WordPress Plugin

5 min read

I just wrote up a quick description for the IndieWeb plugin for WordPress. As a native IndieWebber, I thought I'd PESOS it from GitHub and share it out for those who might be interested. It's also a somewhat self-contained description why one should join the movement and points to some great resources.


The IndieWeb Plugin for Wordpress is a bundled installer for a core set of IndieWeb-related plugins. It's meant to be a one-stop shop to help WordPress users quickly and easily join the growing IndieWeb movement (see below). Some of these sub-plugins are required while others are optional.

Some of these plugins allow you to:

  • send and receive comments, likes, reposts, and other kinds of post responses using your own site
  • allow comments on others' sites to show up as comments on your posts
  • help make IndieWeb comments and mentions look better on your site
  • allow support for threaded comments and webmentions
  • more easily syndicate your content to other sites to take advantage of network effects and other communities while still owning all of your original content
  • link to syndicated versions of a post so that comments on your content in silos like Facebook, Twitter, Instagram, Google+ can come back to your original post as comments there
  • allow you to add bookmarklets to easily respond/comment on other sites with one click
  • set up a MicroPub Server to use other posting interfaces. (You could potentially use services like Instagram, Foursquare, and others to post to your WordPress site.)
  • set up a personal URL shortener
  • log into your WordPress site with services like Twitter, GitHub, SMS, or even email using IndieAuth.

The IndieWeb

The IndieWeb is a people-focused alternative to the ‘corporate web’ that allows you to be the humb of your own web presence. It's been written about in Wired, The Atlantic, Slate, and Gigaom amongst others.

The IndieWeb, like WordPress, feels that your content is yours

When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.

The IndieWeb is here to help you be better connected

Your articles and status messages can be syndicated to all services, not just one, allowing you to engage with everyone in your social network/social graph. Even replies and likes on other services can come back to your site so they’re all in one place.

Interested in connecting your WordPress site to the IndieWeb? Let us help you get started.

Frequently Asked Questions

How do I get Started?

IndieWeb for WordPress includes a plugin installer program. A Getting Started Guide can be found under Plugins->IndieWeb.

Where can I find help? Can I contribute?

A group of web developers (including those knowledgeable about WordPress, among many other web technologies) can be found discussing and working on IndieWeb related technologies in the wiki at or in the IRC on Freenode. WordPress specific portions of the IndieWeb camp can be found at WordPress, Getting Started on WordPress, Examples, and other plugins.

If you need additional assistance, feel free to reach out to any of the WordPress Outreach Club members via the website, our individual websites, or our social media presences -- we're happy to help!

Why IndieWeb?

Find more information and details for the motivations for joining the IndieWeb at

What about plugin XYZ?

If you think we missed a plugin reference, please file an issue on Github.

What plugins are included in this package? Can I install them separately?

  • Webmention (Required) - allows you to send and receive by adding webmention support to WordPress. Mentions show up as comments on your site.
  • Semantic Linkbacks (Required) - makes IndieWeb comments and mentions look better on your site.
  • Webmention for (Threaded) Comments - Adds support for threaded comments for webmentions.
  • Webactions - Adds webaction markups to WordPress elements.
  • Post Kinds - Allows you to reply/like/RSVP etc to another site from your own, by adding support for kinds of posts to WordPress.
  • Syndication Links - Adds fields to a post to allow manual entry of syndication links as well as automatically from a supported syndication plugin. Fully supports Social, partial support for NextScripts: Social Networks Auto-Poster (aka SNAP).
  • MicroPub - A MicroPub Server
  • IndieWeb Press-This - Adds IndieWeb markup to the WordPress Press-This bookmarkets to allow you to respond on your site with one-click.
  • Hum URL Shortener - A personal URL shortener.
  • Indieauth - The plugin lets you login to the WordPress backend via IndieAuth. It uses the URL from the profile page to identify the blog user.

One could certainly download, install, and activate some or all of these plugins separately, but it is much quicker and easier to utilize the interface provided by this IndieWeb plugin to install and activate them. Note that some of these plugins may only be available on GitHub and are not yet on


Also posted to GitHub:

wordpress-indieweb/ at ee1cfb72203f1feef05b9225c4bb465abc82e094 · chrisaldrich/wordpress-indieweb


#IndieWeb Raison d'etre #55: Freedom of the press trumps atrocious comment moderation

2 min read

Last week I wrote up "Some Thoughts on Academic Publishing" after reading “Who’s downloading pirated papers? Everyone” from Science | AAAS which made some heavy rounds in social media, particularly in academic spheres. Originally I began typing my thoughts/comments into the Disqus box on their website. After getting to the third graph, I began thinking, I should be writing this on my own website as a standalone comment/piece of content and just POSSE it over to their Disqus box.

Despite the fact that the editors/moderators of one of the most venerable science journals of our day will allow internet trolls like CPO_C_Ryback and CPO_C_Rybacks_Mother to go thirty rounds on nearly every comment on their featured piece for the week, my slightly more tempered comment is still sitting in their moderation queue untouched. 

My poor pending commentary

Fortunately I had the foresight to have self-published it before hand, or the not-insignificant time I spent thinking and writing about the topic at hand would have been gone the moment I pressed send. It's one thing to get lost in the shuffle of hundreds of comments amidst trolls, it's another thing altogether to be moderated out of existence. The IndieWeb movement has prevented me from feeling like I did two decades ago after writing a term paper for hours only to lose it after discovering that I hadn't hit control-s to save what I'd written. The additional benefit was that I was able to post those same thoughts on multiple other networks effortlessly while still being able to own what I'd originally written.

The greatest irony of the whole affair is that in conjunction with the particular article I was commenting on, Marcia McNutt, Editor-in-Chief Science Journals, published a companion piece about the high costs and attention to detail and quality that journals try to maintain in their digital presence. Apparently this massive expense and terrific effort doesn't go as far as preventing internet trolls like those mentioned from running roughshod over their own site (which is "moderated" by the way) while keeping out commentary that may add to the discussion and community that they're apparently not attempting to foster.



An Annotated Domain of One’s Own

2 min read

Jeremy, Congratulations on having your own domain! I was poking around today and was excited to see that you'd moved over from Genius.

I'm impressed that you specifically mention the IndieWebCamp philosophy, which I've also been using for the past couple of years myself.  If you need some help in IndieWeb-ifying your WordPress install, I'd be happy to help, though it's now much, much easier to do than it was even a year ago. Shortly, I'm hoping to finish up a post about the IndieWeb and academia/educational related sites, which might also be helpful, though I'm not sure when that's actually going to be finished.

I'd love nothing more than to have Hypothesis be able to have webmention support so that when people annotate my own pages or reference them across the web, the system would automatically send me a notification of that fact. Are there any coders at who are also part of the IndieWeb movement who might consider doing this? Is there a way to help suggest this into's roadmap?

Finally, as a side-note, to help beautify your web presence a bit, you might notice that your photo doesn't show up in the author position in your 2016 theme on single posts.  To fix this, you can (create and) use your username/password to create an account on their sister site Uploading your preferred photo on Gravatar and linking it to an email will help to automatically populate your photo in both your site and other wordpress sites across the web. To make it work on your site, just go to your user profile in your wordpress install and use the same email address in your user profile as your gravatar account and the system will port your picture across automatically. If necessary, you can use multiple photos and multiple linked email addresses in your gravatar account to vary your photos.

Congratulations again!


Sharing from the #IndieWeb on Mobile (Android) with Apps and @WithKnown

4 min read

I've been doing some work to find a better, easier, and cleaner way to share content, likes, replies, bookmarks, and reposts on mobile. In part it's what prompted me to write my post the other day about "Configuring the RSS Reader Woodwind for Known."

In part, I want to keep a complete record of posts that I "like", "share", "retweet", etc. on my own site, in keeping with the principles of the indieweb. Between separate indieweb installs of both WordPress and Known that I've been using for roughly the last two years, this hasn't been difficult on my laptop computer, primarily making use of a bevy of bookmarklet tools in my browser. In fact, on my laptop, it's down-right simple.

But not so on my Android mobile phone! In fact there, it's actually a really painful experience, and as a result I sometimes retweet, like and carry on in the Twitter app like the IndieWeb movement is dead to me. As a result I feel continually guilty and carry around a lot of . So I put out a call for help and got a few responses [1] [2] with some ideas. 

After playing around for a few days with two different apps, I thought I'd post some thoughts about the two different solutions, which to me are roughly the same.

Bookmarklet Free, which I found on Ryan Barrett's site which included some generally excellent instructions wasn't too bad.

URL Forwarder, was recommended by Tino Kremer, didn't include any instructions or hints at all.

Fortunately, both work roughly the same and the set ups aren't all too different for some of the set up for configuring Woodwind, mentioned above. Testing them out with Known allowed me to click the ubiquitous sharing icon in most Android apps that then triggered a pop-up allowing me to choose which app I want to share with.  Selecting either Bookmarklet Free or URL Forwarder then took me to an interstitial screen to let me choose whether I wanted to like, share, repost, bookmark, or reply to the particular content.

In most cases both bookmarklets did a reasonable and similar job, but typically they ended up sharing a section of unwanted text followed by a URL (and sometimes---depending on the app---another chunk of text related to the original content).  Typically I had to delete the extraneous "titling" text to leave the raw URL which Known then did a good job of reformatting properly to allow me to finish the post and send it off. (Kyle, Ryan, and Kevin had a short discussion on the handling of the "title" back in the day, which Known apparently hasn't implemented, but Ryan proffers some Github code to remedy the issue within the CMS.)

Between the two, I generally prefer the UI and set up for URL Forwarder a bit better. Both are roughly equivalent.

Since Ryan did a good job showing the configuration settings for Bookmarklet Free in his post, I'll include the similar settings for URL Forwarder for those using Known:

One need only to replace `` with their appropriate site URL.

Here, the action name, which appears first, is what I put in for the "Filter name" (field 1). The URL which follows was what I used for the "Filter url" (field 2). For each of these one should leave the "Replaceable text" field as "@url".

Screenshot Screenshot 2

Nota bene: I'm using the KnownReactions plugin to provide functionality for the "like" and "repost" types and that without it, these action types won't function properly on your Known installation.

Those at Known, are more than welcome to freely cut/paste/modify this for potential inclusion into their documentation for future use.

If anyone has other suggestions for improved posting via mobile, I'd certainly love to hear them!


Configuring the #IndieWeb RSS Reader Woodwind for @WithKnown

4 min read

Woodwind (so, named because it's part of the "reed/read" family), is a nice little RSS program for following and interacting with blogs and sites as part of one's regimen.

Today, I began setting it up in conjunction with my self-hosted Known [download] site which also has Kyle Mahan's "KnownReactions" plugin installed. This plugin allows me to "like" and "repost" content on the web in addition to Known's built in "share", "bookmark", and "reply" functionality.

I played around on my Known site with some various options to configure Woodwind which has several built in reply mechanisms available:

Reply Mechanism

  Each post will have Like, Repost, and Reply buttons that will post content to your site directly via micropub. See Micropub for details.

  Clicking an indie-action link will invoke your web+action handler if registered. See indie-configfor details.

  Manually configure your own web action handlers. The placeholder {url} will be replaced with the permalink URL of each entry.

These variations are primarily based upon the type of site and architecture you're using to take the content from the reader and post it to your own site.

I tried out Micropub, which Known supports automatically, and liked the interface, but it didn't give me as much flexibility as I would have liked in terms of post types. (The stars it posts up for likes are a tad unwieldly too.) I'm honestly not sure if Known supports the Indie-config option, though my guess is that it doesn't. (I'm thinking that building a WordPress plugin to allow easy plug-and-play for Indie-config would be fun on an alternate CMS platform, but I'd guess that David Shanske likely already has.)

I finally messed around for a while with trying to get the Configurable action urls option working on my Known site. It seems to be working pretty well now, so I thought I'd pass along the very simple hack so that others who are less tenatious can relatively easily cut and paste the solution to get their Woodwind configuration humming more quickly.

Each action get's a title, which appears on the associated buttons within Woodwind, which is followed by a custom url.  I'll list the most common ones for Known below:

One need only to replace `` with the appropriate site URL, thus in my case for the "Share" button, I used `{url}&share_title=&share_type=note`.

I imagine that one could also use this general format to create buttons within Woodwind to post comics, recipes, and even reviews using the community plugins for Known, though it's likely that some of these plugins may need some tweaks to work properly.

Again, I'll note that I'm using the KnownReactions plugin to provide functionality for the "like" and "repost" types and that without it, these buttons won't function properly on your installation.

Those at Known, are more than welcome to freely cut/paste/modify this for potential inclusion into their documentation for future use.


The IndieWeb Movement and Drupal

3 min read

The IndieWeb is a growing people-focused alternative to the ‘corporate web’.

This BoF session is encouraged for all levels of Drupal users: beginner, intermediate, and advanced. Developers, and particularly those working for larger corporations, should be interested in the benefits that some of the IndieWeb principles can convey to the marketing/communications departments of their clients' companies.

Haven't you (or your clients) always wanted to be the "hub" of your own online presence with ancillary social services helping to serve your purposes rather than the services' own interests? Isn't this why we all want to build and have our own online spaces in the first place?

With the rise of areas like social media, it's often the case that much of our content and material lives in corporate silos like Facebook, Twitter, Instagram, Pinterest, and a variety of other sites. Sadly, as netizens, we do not have direct control over these sites, often can't export our data from them, and they can be (and often are) bought out or shut down at almost a moments notice. Worse, comments and interaction with our content is typically also stuck in these silos and it lives or dies with them. Wouldn't you love to have the network effect and value that these sites bring without the extra work or hindrances they bring?

There is a growing and very viable alternative to this model which is being built by the IndieWebCamp community as a multi-platform and opensource project which dovetails well with the ideals of the Drupal community.

Those who are interested in learning about and discussing some of the basic principles and philosophies of the movement are encouraged to attend. We'll chat about some of the current projects and capabilities as well as open standards that help enable the functionality you've always wanted (or maybe didn't know you wanted until now) in your websites.

Moving forward, we can all build IndieWeb principles into the Drupal platform to help it remain relevant as the web continues to grow and evolve.

A wealth of information about the IndieWeb community can be found at their website, but as a brief overview some of their basic principles appear below:

Your content is yours

When you post something on the web, it should belong to you, not a corporation. Too many companies have gone out of business and lost all of their users’ data. By joining the IndieWeb, your content stays yours and in your control.

You are better connected

Your articles and status messages can go to all services, not just one, allowing you to engage with everyone. Even replies and likes on other services can come back to your site so they’re all in one place.

You are in control

You can post anything you want, in any format you want, with no one monitoring you. In addition, you share simple readable links such as These links are permanent and will always work.

Category: BoF

Skill: Beginner

Duration: One hour

Session Tags: IndieWeb, social media, Open Source, web architecture, open standards

Register for the session at 2015 Drupal Camp LA at


Updating @WithKnown Past 0.7.7 and Keeping Social Media Integration

3 min read

Last night I upgraded my WithKnown installation from 0.7.5 to and was shocked to see all of the social media integration of my instance had completely disappeared!  

Suddenly POSSE wasn't POSS-I-ble!

Starting with 0.7.7, Known had taken out the old social media plugins and replaced them with Convoy. While I'm sure Convoy is awesome and makes social media integration for POSSE dead simple, something in my gut told me that it just wasn't for me.  I also didn't want to throw away the hour or so I spent configuring all of the plugins in the first place only to end up paying $50 a year for the same thing I'd already had. Those who haven't dealt with it already, will probably find Convoy a great value, though it'd probably be better billed as a one-time fee rather than a recurring one.

I'll admit that I panicked for a while and contemplated restoring the original 0.7.5 server code from back-up.

Fortunately a cooler head prevailed and some research and internet searching began.  I didn't find much immediately - the drawback of living so close to the bleeding edge of technology when still learning how all of it works.

I tried to see if I could uninstall the Convoy plugin by going into the site configurations and changing the plugin to disable it. Sadly, of the dozen or so plugins, Convoy is the only one that didn't ship with an "enable"/"disable" button. I'm sure they'll fix this shortly, but for those who want to do it manually, simply add the following line of code to your config.ini file:

     antiplugins[] = 'Convoy'

Screen capture of Plugins Settings Page

Eventually, I spent some time digging into the code and comparing/contrasting all the files.  Noticing that 0.7.6 had six or so additional folders for each of the social media plugins hiding within the IdnoPlugins folder (Facebook, Twitter, Flickr, SoundCloud, etc.), I simply dragged and dropped all of those over into and voila! We're back up and running.

As a fine point, one should notice that both the FourSquare and Twitter plugins have been updated since 0.7.6, so they should be copied and dragged over from the main GitHub repository.  Following a similar procedure will also need to be watched/followed for future updates on occasion as well.

For future UX, I'm hoping that Known will at least as a minimum install and make Convoy available directly, but that disabling it will make the other original plugins viewable and configurable for the more technically minded, particularly as POSSE is one of the cornerstones of the IndieWeb movement.

As a quick recap for those doing general Known upgrades, try the following:

  1. Back up your database and your code, just in case;
  2. Download the new repository (either GitHub or on WithKnown);
  3. Delete the "dummy" Uploads folder from the new install and keep your original on the server which has all of your photos, etc.;
  4. Keep your config.ini; 
  5. Keep your .htaccess (unless it needs a serious change; the htaccess.dist replacement file can be easily copied over, but will need to have its name changed from the version with the .dist extension);
  6. Keep the social media plugin folders in IdnoPlugins that you intend to continue using; or upload newer versions which are availble from ​;
  7. Upload all the new files to the server directory.

Those with an adventurous spirit may also find some of the other available plugins fun to play around with too.