September 02, 2010

Revisiting the wave


I was reminded of the Google service called 'Wave' when I saw the article: Joined the wave.
So I just went over there to see whether it looks any different from what it used to be. I had read some tweets and news about Google discontinuing the development on wave ,some time back.So, I wasn't really expecting anything above the slow and unresponsive windows and cluttered boxes which is my memory of Google Wave.

Though the activities and presence (or lack of) of online contacts in wave supported by expectations, the interface and its responsiveness looked better than it used to. Maybe if, initially itself, they had released it the way it is now, it wouldn't have had this sudden death. Considering the hype that surrounded it during its beta release time, it has been a real nail in the coffin for the internet giant, that is Google. With this and some more failures and partially successful ventures, Google has been gaining on the negative opinions scale, competing with the likes of Microsoft and Facebook.

Coming back to wave, the thing that caught my attention was the 6 boxes under "Start a New Wave", namely 'Blank Wave','Discussion','Task Tracking','Meeting','Document' and 'Brainstorming'. As there weren't any contacts online, I was not interested in any of these, except 'Task tracking' and 'Brainstorming'.

But, each of them turned out be something like a custom template from Google Docs.Brainstorming had this extra feature of flash component that allows drawing. So, for collaborative brainstorming, this might have been a good tool. I liked that.

Speaking of the task tracker, I being a person of low brain retentivity, tend to use task trackers and notes extensively. And hence, I find such tools very useful and amusing. Here also, the availability, of categorization of tasks based on priority caught my attention. Apart from that, it is not interesting at all. I would any day prefer a proper task planner software on my desktop, or for that matter, even gmail's task list over this.


Overall, I felt good that Google stopped wasting time on this. Maybe they will enhance something else worth using. It was rightly discontinued, as it is a big failure from Google. So waving goodbye to Google Wave again..adios

Echofon breaks in Linux

One fine day,when I logged onto my Ubuntu, and started firefox, I got a message box with no contents in it other than an OK button with the message box title reading 'Echofon'. As I couldn't figure out what was causing this error, I executed Firefox from the terminal in background mode. The error message that was printed on the terminal is :
"Can't get OAuth signer. Use Basic Auth instead. / Cc['@naan.net/twitterfox-sign;1']"

I googled this, and came to Echofon for Firefox, where many people have put their comments that Echofon is broken for Linux or has been discontinued for Linux from version 1.9.6.5 onwards.

Mine was that version, and so as per the suggestions in that page, I reverted back to version 1.9.6.4,and voila echofon is working fine.

Morever I saw that Twitter has sent me a mail regarding discontinuation of basic authentication and enforcement of "OAuth" authenatication method. This might prove useful in centrally controlling all applications which have access to twitter timeline.

But the news of rolling out of "t.co" url wrapping doesn't sound so good, in spite of their claims of providing protection from potentially malicious website and reducing obscurity in URLs provided over twitter.

With this in place, I wonder what would happen to services like bit.ly which provide realtime analytics for such shortened links. Anyway it will be deployed in a beta mode in a couple of weeks, and made mandatory by end of the year. So, have to wait and see what happens, and how tweeples react to these new regulations and rules in twitter,.