As many of you know, I’ve been doing some contract work with Bit.ly since this past July (super awesome place to work and full of top notch talent btw).
Anyway, internally Bit.ly (and much of BetaWorks) uses the Adium chat program to communicate and as such, there are always a lot of really interesting links flying around the office…but very few of those links were actually bit.ly links (because the staff is too busy doing the more serious work that makes bit.ly as great as it is to take the time to write a plugin).
But I thought it sounded like a fun and interesting side project to take up (I hadn’t used Adium before, but I was already dabbling in Objective C for some iPhone stuff)…and so I took a few nights and wrote a simple plug in that will use the bit.ly API to automatically shorten any link you share (great for tracking how many clicks the links you share via adium generate!).
I released it to the Adium Xtras directory at the end of July…and basically moved on to other projects that were interesting me.
But in the last couple of days, I’ve started to get people pinging me on Twitter about the plugin…most notably that, while they like it and all, it doesn’t quite do what they want…because by default the plugin just uses the global bit.ly account, which means you can’t really determine how many clicks you specifically generated. Kinda defeats the whole reason most people would want this plugin, no?
To be honest, I had the same reaction when I built the first version, and so I did go ahead and write in some support for using your own apiKey way back in July.
However for a handful of reasons (mostly my laziness), I had not gotten around to releasing it to the Adium Xtras directory…to be fair it takes awhile for the volunteer Adium team to review and approve changes and I was waiting on the initial approval before I could submit a change…once I got the initial approval, I just never got around to submitting the update – cause, well, I’m VERY lazy.
Anyway - today I FINALLY got around to submitting the update…but since it will take some time for them to (hopefully) approve the udpate…so I’m also releasing it here for those that don’t want to wait.
32 Bit Version: 32 bit Bit.ly Adium Plugin
64 Bit Version: 64 bit Bit.ly Adium Plugin
Since you’ll most likely want to To use your own Bit.ly apiKey…I recommend you grab one of the above zip files (btw - I only submitted the 64 bit to the Xtras directory), extract it, then double click the plugin that gets extracted (this should take care of the actual Adium install).
Once it’s installed, you can then go ahead and configure it with your own Bit.ly login and apiKey (if you don’t know how to get that stuff from bit.ly login to your bit.ly account and then check out http://bit.ly/a/account)
Here’s how to configure the plugin to use your bit.ly apiKey:
1. On your local Mac. create the text file ’Library/Application Support/Adium 2.0/bitly_api.txt’ (if you installed Adium in a non standard location, then you may need to track down the location of your Adium 2.0 folder)
2. The contents of the file should be in the following format:
…Make sure you replace the YOUR_BITLY_ASSIGNED_KEY and YOUR_BITLY_LOGIN with your account specific details…and though it’s not entirely required, it’s probably best to just keep it all on one line.
3. Once you create and save this file, make sure you restart Adium
…and you should be all good!
Keep in mind that this is really a quick hack, and probably not all that stable…and there’s a good chance it just won’t work for some of you because Adium is a bit chaotic under the hood and honestly my understanding of it is SHAKEY at best (hopefully it does work for most though).
Anyway - good luck and as usual if you have troubles, questions, or comments, feel free to email me at info at falicon dot com any time.
This post has received 41 loves.
Kevin has a day job as CTO of Veritonic and is spending nights & weekends hacking on Share Game Tape. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at falicon.com.
If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).