At 37signals, Backpack’s Journal feature answers the “Hey, what are you working on right now and what have you done lately?” question.
We wanted to make it easier to get journal entries into Backpack so we added a tiny wrapper around the existing journal API to make it work with a couple of StatusNet desktop clients (Adium is probably the most famous one). Now you can follow everyone else’s journal updates and make your own updates directly from a desktop client.
Here’s how you can use Backpack journal entries with the latest Adium.
1. Add a new account for StatusNet
2. Enter your Backpack username and password
3. Specify your Backpack account url and path
Be sure to select “Encrypt connection using SSL” option.
Now you should see “Timeline (username)” in your Adium contacts list.
If Adium isn’t your cup of tea, we tested another client which has more twitter-ish feel to it : Spaz
Here are Spaz settings :
Base API URL : https://url.backpackit.com/journal_entries/api/
Base WWW URL : https://url.backpackit.com/journal_entries/api/redirect/
This should work with a variety of other desktop clients as well. But we’ve only tested the two mentioned in this post.
Backpack journal is an integral part of our work day and we’re checking it constantly to see what everyone is working on. Now we can get instant notifications about new journal entries and add new entries without going through a browser.
John
on 02 Nov 10Journal integration with campfire would be a HUGE win. Por favor. :-/
birtulove
on 03 Nov 10dfsadvz
Cristoffer
on 03 Nov 10Hi, it does not work for me. I get the updates from Backpack to Adium, but I get “Connection error” while trying to post to the journal from the Adium client. Settings as above. Any suggestions?
Mike Cottmeyer
on 05 Nov 10Having the same issue.. a connection error occurred. Not getting traffic either way.
Kris
on 05 Nov 10What if I login to backpack using openid?
Pratik
on 06 Nov 10Cristoffer/Mike,
Just to be sure, are you replacing ‘your_account’ in url with your actual account url ? Could you please submit a support request if the problem still persist ?
Thanks.
This discussion is closed.