I do a lot of my day to day work on Github, as you may have noticed. So, to be a good #indieweb citizen, I figured it’d be nice to be able to at least comment on tickets from my own site.

Thankfully, Github has a pretty comprehensive API, so it turns out that doing this was pretty easy. So, I wrote a quick plugin for Known…

Github ticket and comment syndication

Install and activate the plugin in the usual way, and once enabled, you will have the ability to reply to comments and create tickets on Github. This is particularly useful when using the Known browser extensions (like my Chrome plugin).

To create a new ticket, make a reply to a plugin’s issues page, and to create a new comment, simply reply to the comment thread.

Let me know how you get on!

» Visit the project on Github...

So, a few months ago, Flickr decided to change their terms and conditions so that they could sell your Creative Commons photos. This got a lot of people’s goat, myself included since I’m a paid user, and have been for a while (as an aside, had Yahoo done it as a profit share, it would have been awesome for everybody, but noooo…)

Because self hosting in this post Snowden world is only ever going to be a good thing, I don’t want my family photos used in corporate branding without a cut, and because I wanted to be a good #indieweb citizen, I thought I’d take the plunge and move to self hosting.

I’ve tried this before with Trovebox Community Edition but didn’t have much success – while their Flickr data export seemed to work, the import didn’t. They’ve probably got it working by now, but I pretty much gave up.

Anyway, since I’m a contributor to Known, I thought I’d dogfood and hack together an importer.

Flickr Importer for Known

The importer works by calling the Flickr API using credentials stored in your linked Flickr account. To do this, it uses the Flickr syndication plugin to do the donkey work of linking your accounts.

Once activated, and your Flickr account is linked, you are given the option to run an import.

The import job will run in the background, and will import all your photos and videos into your photostream (using the Photo and Media plugins which should also be activated), preserving timestamps, titles, body and tags.

At the time of writing I’ve not got it importing photosets and collections, since Known currently lacks a logical mapping, but I’m keen to at least record this information for later processing. The script will import sets and collections as generic data items, which you can expose by writing support into your theme.

The plugin records state, so it should recover from crashes, and you can re-sync safely at any time.

Have a play and let me know what you think! Pull requests are of course welcome.

» Visit the project on Github...

So, I’ve been using Known to post to post status updates for a little while now, the latest of which you can see in the sidebar on the right hand side (which is displayed using a WordPress plugin I wrote).

Known also lets you reply to messages directly from your site (replying to other sites that enable webmentions, twitter, or even Github), but unfortunately, while Known has a configurable timeline (so you can choose what content to display by default) the standard Known status message plugin doesn’t differentiate between posts and replies.

Because it was bugging me having my timeline filled with reply messages to various places (which were out of context for most people) I wrote a patch for the Status plugin that will allow you to differentiate between messages and replies in both the content type selector and the homepage configuration tool.

My timeline now shows everything by default, except replies (you can still see those if you select “All Content” from the selector), and this is also reflected in my sidebar!

I’ve submitted this as a pull request upstream which has yet to be merged, but in the mean time you’ll need to apply the patch from my development fork.