Known comes bundled with a Firefox plugin that, using Mozilla’s Social API, allows you to add a Known share/reply button to your browser.

This is pretty cool, but sadly only works for Firefox.

While other browsers, including Chrome, can use the bookmarklet to access the same functionality, this is rather clunky – for one thing, Chrome’s bookmark bar is hidden by default, for another Chrome has an extensive API and it’d be a shame not to use it!

A Chrome plugin for your site

So, I had a go at putting together a Chrome plugin… partly to scratch this itch, but also to learn how to write Chrome extensions (which turns out to be fabulously easy).

Install and activate the plugin, then go to your settings page to download a chrome extension which has been customised to your site.

Go to your Settings -> Extensions page, and then drag the archive into the list; all being well, you’ll have a new icon next to your address bar!

» Visit the project on Github...

I have previously introduced a plugin that adds Bit.ly link shortening capabilities to the Known sharing tool.

I just wanted to post a quick update to note that I have now added full OAuth2 support to the plugin.

Previously, integration was provided by the Generic Access Token, which meant that you could only have one Bit.ly account associated with an install. With OAuth2, each user on a given Known site will be able to link to their own bit.ly accounts (with their own vanity urls if they wish).

Pretty neat!

» Visit the project on Github...

So, Known lets you share links via a share API (and a toolbar bookmarklet). In the later versions of it, this action also calls a link shorten event hook which allows a plugin to shorten the shared URL.

Because I often share links, I wrote a quick plugin to hook into my bit.ly domain.

Using the plugin

Install and activate the plugin in the usual way, and then in your admin panel add your generic access token to the input box on the bitly page. Generate this token from your bitly settings page.

Currently you can only have one domain per Idno install, basically because I was short of time and so didn’t do the full OAuth thing.

So much to do, and so little time. Have fun!

» Visit the project on Github...