Cubicgarden.com…

I partly talked about this before but theres been a series of updates which I couldn't help but blog about.

So I was talking to Miles about a client which could support much more that Microblogging and we were suprised that no ones actually built a clever client app which supports Microblogging + RSS + XMPP? Well the closes we can find to that idea is a OSX application called Eventbox. Actually this blog entry does a much better job explaining what it can do, and what a difference it means for advanced users.

If you imagine the dashboard of Facebook (credit to Stowe Boyd) but under your control using the services you prefer. Fan of Flickr, just add them and the RSS feed. Prefer photobucket use that instead. Its a bit like the life streaming services such as Plaxo, Mybloglog and Friendfeed. The application/client should be clever enough to look at the service and work out through maybe some discovery service/xml whats possible with the service. So for example adding Twitter will allow you to post and read, while a flickr feed won't. It would be cool to also finally start adding some of those comment services into the mix, so for example allow backtype comments if you start adding stuff to a RSS feed from a blog. Hell why not add a proper metaweblog/atom Blog editor too maybe?

Anyway, Eventbox is close and seems to be on the right track and I was starting to get worried that once again the linux platform would be left behind in this area. But I was wrong actually deadly wrong because under my own nose was Gwibber.

I've been using it for a while now and its actually fended off competition from Air apps like Twitterdeck (far too twitterfied) and Twirl (crashes a lot) for my ubuntu desktop. But what shocked me today when talking to Miles was the new supported protocals it has. I had done updates and never knew about the new features.

So now theres support for,

• RSS/Atom
• Digg
• La.conica
• Twitter
• Pidgin
• Ping.fm
• Facebook
• Jaiku
• Pownce
• Flickr
• Indenti.ca

So most of the Microblogging services including the recently defunked Pownce and open source La.conica. RSS including automatic discovery for Digg and Flickr. Then some of the interesting ones, Facebook with the ability to also send messages into the Facebook paywall. Ping.FM support, means you can send from Gwibber to all those other services such as Brightkite, Rejaw, etc, etc. But the one which is strange and most exciting is Pidgin support. The problem is, there is no documentation for the Pidgin part and the account says you can send only. So after some playing around, I worked out that when you send a message on Gwibber, it will also set the status of Pidgin. This is cool, but I also want the ability to recieve XMPP messages straight into Gwibber.

Actually Gwibber has the structure to really move forward. I've already seen multiple types of authentication from username/password to a Oauth like facebook auth. Each protocal gets its own colour which you can set and you can enable recieve, send and search on each one (protocal supporting). Search works well, but I'll like to see some kind of watch or a pounce system like you get in Pidgin or Specto. Finally it would be useful to support the Newsgator API (yep I switched from bloglines to newsgator) for RSS, so you can properly manage the RSS and not end up reading the same news over and over again.

Technorati Tags: gwibber, microblogging, linux, client, stream, flow, eventbox, xmpp, twitter

Comments [Comments]
Trackbacks [0]

One of the things I really missed out on but have been following is the developments around the open stack. I kind of prefer social stack but I can see a lot of benefit to open over social. Anyway, this work has been pioneered by some really good guys including David Recordon, Chris Messina, Sebastian Küpers, etc, etc (sorry to many names to list). Today I was struck by Jyri's blog post about Chris Messina's talk at some event recently.

In his presentation at Friday's event, Chris Messina demonstrated the use case of subscribing to someone who lives on a foreign Web service.

In what follows I'll expand on Chris' story by discussing another use case, where you add the
foreign friend to your address book without needing to go to their site.

Imagine I want to add a friend, David Recordon to my contacts. I
know his email address, so I click 'add contact' in my client and enter
his email.

My client translates David's email address into his OpenID URL, probably using a method called Email to URL Translation.

Now that my client knows where to find David on the Web, it goes out to David's URL and fetches a little file that contains machine-readable pointers
to David's public profile and the photos, status messages, bookmarks,
blogs, and other feeds he publishes. The enabling standards at work
here are likely to be XRDS-Simple and Portable Contacts.

This loop is simply referred to as 'discovery'.

Once my client is done, it is ready to display its findings to me.
Here's a mock-up to illustrate what I might see (the same mock is in
Chris' slides):

After selecting David's contact information and some of his feeds, I
click 'Save', and a subscription request is sent to these services. They
return a few of David's most recent public updates to me.

The next time David logs into these services, he sees a standard new
subscriber notification. His service can perform discovery on me to
display my name and profile summary to him, and allow him to
reciprocate.

David may also choose to allow me to see some of his private information, such as his contact details. The enabling standard here is of course OAuth.

I have never needed to join any of the services David uses; in fact,
I don't even need to know their names. It is irrelevant to me if he
uses Twitter, Plurk, or Friendfeed to publish his status updates or
prefers Flickr, Photobucket, or Picasa for sharing his photos. All I care about is seeing his updates and being able to respond to them using my own client.

Information wants to be free, and social objects want to travel.

The thing this reminds me of, is when Tim Burners-Lee wrote about the Semantic web and how agents talk to services, etc. You can follow how it works without even knowing the different technologies too well. So while these guys figure out the webside of things, these other guys earn a mention for there work on the services stuff and Controlyourself for there work on openmicroblogging.

Comments [Comments]
Trackbacks [0]