Well, the clocks have gone back, and the nights are drawing in. If you’re anything like me, this means you just want to find somewhere warm to curl up in until spring.

But before you do, I would just like to point you to the fact that Known 1.0 is finally out of the door!

It’s been a long journey to get to this point, but I’m delighted to finally get to a point where we can draw a line in the sand.

Crack open the beverage of your choice, and go download Known 1.0 now!

Because I’m currently in the UK, I went along to the Indieweb Camp Oxford event today!

I didn’t really go with a plan, except to sort of see what other people were up to and help out where I could, with a backup plan of doing a bit of Known dev if I could.

In the end I helped guide some folks with setting up their own Known installs, and answer some questions about the Indieweb in general (apparently I’m a veteran now!).

Was a really fun event, and it was really great to hang out with a bunch of like minded smart people!

Temporarily location protected checkins

I had a conversation with one of the attendees, a fellow traveller, and I hit on a hopefully useful extension to the Known Checkin plugin – protected checkins.

Protected checkins will, when enabled for a post, protect your exact checkin location for 24 hours. Logged in users will still be able to see your exact location, as will logged out users after 24 hours have elapsed.

The use case here is for vulnerable people, as well as travel bloggers, backpackers and nomads, who want to share their location but not be particularly precise with the location while they’re there.

So, with this feature, you can check in to a location, but not share your precise location until much later, after you’ve presumably moved on.

Anyway, I thought it was a cute idea, hope you’ll find it useful!

» Visit the project on Github...

There have been a lot of changes recently with Flickr, and from February, free users with over 1000 photos are going to start seeing their old photos being deleted. Premium membership has also seen a sharp increase in price.

So, this seems like an opportune moment to move my photos off the platform – I’ve got something going on to 3K photos on there, and while I still have the originals, I’ve nicely sorted them into albums, so it would be a shame to lose that.

Previous attempts at writing an import tool connected over the API, but this broke some time ago when Flickr changed their authentication mechanism, and honestly I’ve not had the time to fix it.

Thankfully, Flickr now offers a full data export via your accounts page. This export contains a bunch of zip files that contain all your media, as well as handy .json dumps of all the image meta data. Using this seemed like a much better way than fighting with Flickr’s API again.

Usage

The new tool is a Known console plugin, so unlike the previous tool, you’ll need to install this to your ConsolePlugins directory.

Next, you need to request and download all your data from Flickr. Do this via your accounts page.

Once you have your .zip files, place them in a directory somewhere, where you can access them from your Known install.

Next, execute your import by running the import code from the console:

Where username-to-import-to is the user who’s stream these photos and videos will appear under, and /path/to/flickr/export is the directory you’ve stuffed your .zip files. 

There is no need to unzip these files ahead of time, the import tool will do that for you.

After you’ve run the import, assuming that there have been no errors, you should see all your photos and videos appearing on your stream!

» Visit the project on Github...