As of the 1st of September, 2010, Yatca will no longer work with Twitter. The reason is that Twitter no longer supports the ‘basic auth’ mechanism that Yatca uses when interacting with the Twitter servers. The people at Twitter are not even slightly to blame here. I agree fully with their moving away from ‘basic auth’. They gave plenty of notice that this change was coming and they provided lots of advice on how to re-work client apps such as Yatca to use the newer OpenAuth mechanism. The simple truth is that with all the other commitments in my life, I just couldn’t find the time to make the necessary changes. In any case, the official BlackBerry Twitter client from RIM integrates with the Messages application and it was this single feature alone that drove me to develop Yatca in the first place.
I’m now trying to decide what to do with the source for Yatca. There is a lot of stuff in there that might be useful to somebody developing a BlackBerry app that interacts with Twitter (assuming you’re up to coding the OpenAuth bit yourself but it’s not rocket science). Maybe I should just turn Yatca over to the status.net people to see if they could do something useful with it – I really like what those guys are doing. Any other suggestions?