Vivek live and kickin'

Twitter will remove the option to use Basic Auth from June onwards and the only option left is OAuth. But the problem with OAuth is that its a UX nightmare to implement in a Desktop application. After trying to figure out how to use OAuth all day long I finally figured out that I was looking for xAuth all along. Cutting a long story short I found a blogpost which helped me get a hang of it. Using xAuth, an alternate OAuth from Twitter . Also found a little bit of help on the twitter wiki on using xAuth . Its quite simple to use once you get a hang of it. But since it mentions headers in most of the places I assumed HTTP headers but you need to provide all the parameters when you POST it to twitter. I have sent out a mail to enable xAuth on my account lets see how long that takes and I can finally start using xAuth instead of the cumbersome OAuth to log into twitter.

Its been two weeks since I started with it. Have not done any real programming lately just been busy with the UI of the application. Tested out the API's and they seem to work. Most of the ground work has been done. The basic prototyping is done and things seem to work. The best part is that till now the size of the final executable is less than 50 kilobytes. Also have been looking at ways to make sure that the application auto updates with almost zero effort on the users part. For now I have decided to use the basic authentication instead of using oAuth. With oAuth it will be difficult to log into twitpic and bit.ly . These are two basic services that I want in the pre-alpha release. The UI has been quite challenging. The main thing is that it should look and feel like a windows application while having all the features of the AIR based Twitter clients. This is important as most of the users are used to these applications. Still quite a long way to go before I can release anythin...