Twitter's OAuth Authentication, Twikini, and Windows Mobile

As early as April this year, Twitter announced that it will drop third party applications’ authentication other than OAuth to connect to Twitter, and it happened in September 1, 2010. That means that authentication methods like keying in your username and password will not work anymore.

The OAuth method means that in order to use a desktop, mobile or online application to interface with Twitter, you will need to click a link that will bring you to the Twitter page (see sample screenshot below) to authorize the connection.

Examples of desktop applications are Tweetdeck, Seesmic, Twhirl, etc. Examples of online applications are Twitter on Facebook, Friendfeed, Twitpic, and even the various WordPress plugins. For Mobile phone, well, there are different applications for each operating system (e.g., iOS, Android, BlackBerry’s RIM, Windows Mobile, Symbian, etc.).

I have read or heard from various blogs about Twitter’s absolute use of OAuth authentication. But I ignored it, thinking that I don’t develop twitter applications and so that should really be least of my concerns.

Until now, when I found out that I couldn’t use my Twitter app for Windows Mobile, Twikini, anymore.

[adsense]

Twikini

Twikini is a Windows Mobile client for Twitter. It’s actually one of my favorite WinMo Apps that I paid $4.95 for it to the developers, Trinket Software. It’s lean and fast, just as the developers describe:

FAST! Unlike other Twitter apps for Windows® Mobile, Twikini is written entirely in native C++ code for maximum performance and the fastest load time possible.

The software I paid for comes with free future upgrades, should there be any. Actually, without further upgrades, that latest version of Twikini I installed was already fully functional in its own right. There were a few bugs but ignorable, which usually only occur when there are connection issues.

However, starting September 1, I discovered I couldn’t open Twikini anymore, and it kept asking for my Twitter login credentials. I supplied the correct username and password –yes, but nothing is doing right. Then I read around and it has got to be because of Twitter’s new authentication policy.

And the worst thing about it is Trinket Software already stopped updating the software for my version (6.5) of Windows Mobile.

Sorry guys, with the shape WM 6.x is in, we've moved on to other projects. Twikini will be back on WP7.

Pls note: Twikini will likely stop working later this month (see http://www.countdowntooauth.com). No further updates are planned.

Now, ain’t that great? I paid for a software thinking it comes cheap for a fully functional Twitter application, when it was actually worthless to begin with. I felt like I was robbed by Twinket Software with a few dollars by selling me trash.

The Blame Game

Yet, at the end of the day, Twikini stopped working to connect to Twitter in Windows Mobile. Who’s really to blame?

On one hand is Twinket Software, the developer of Twikini, for reasons discussed above. On the second is Twitter for dropping authentication methods other than Oauth. The third and the last, Windows Mobile, for being abandoned by users and application developers alike.

More related readings about Twikini and Twitter’s OAuth

Twitter's OAuth Authentication, Twikini, and Windows Mobile

3 thoughts on “Twitter's OAuth Authentication, Twikini, and Windows Mobile

  1. I also paid the few quid to Trinket for Twikini, and at least I had a few useful months out of it before the oAuth upgrade rendered it obsolete.

    I was very disappointed and slightly frustrated (and I let Trinket know, politely) – but I also reminded them that I like it a lot and can’t wait for a new version for WinMo down the line! Hopefully they’ll also realise that everyone who paid will probably even pay a couple of quid for the new oAuth version… I certainly would.

    Fingers crossed a new version of Twikini actually gets developed, in the meantime I’m back to using PockeTwit (v0.83 onwards supports oAuth) but I still VASTLY prefer Twikini, it’s faster, leaner and does things like GPS support in a much cleverer way. Here’s hoping. :)

    1. Hi Christopher, thanks for dropping by. Unfortunately, I guess Trinket is not interested anymore with WinMo, especially the 6.5 (unfortunately for me too, the smartphone I have is not capable of upgrading to WinMo 7 should it be out). I’ve even once saw their webpage land in a godaddy webpage, meaning they failed to renew the domain name. At least now it’s back online.

Let yourself be heard:

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s