Can't connect to Twitter again...

[jwpnet]

Have the twitter API updates from months ago. Asks me to authorize Twitter and enter my password. I did that and it says authentication failure. Anyone else?

Why does Tagged not care about this product? It's really the best IM client available. Such a shame that it's going to decay into nothing.

[darkmorpher]

Twitter support possibly won't be coming in the future. They now strictly discourage third party client apps adding twitter support. Check their Dev blog | Link 2

Edit: If you are getting "Bad Authentication data" error, then your app isn't configured correctly to interact with the new API.

[jwpnet]

Maybe I am missing the key lines, but I don't see where they discourage it. It just seems like they want to certify a preinstalled twitter app on devices, and they want to limit the number of tokens an app is given without permission from twitter. They also want the UI to meet Twitter standards. What am I missing?

[Brok3nHalo]

I'm not sure but I think Digsby fits most their guidelines with a possible exception of a few GUI rules, that should be easily tweaked though.

As for the current problem It seems it logs in correctly with OAuth and authorization is successful. However, when Digsby tries to retrieve the list of followed users (using friends/ids.json) it returns an authorization error. I haven't had a chance to look into the cause, perhaps Digsby still uses 1.0 oauth and it requires the 1.1 version to access that API now?

If anyone wants to look into this it's getFollowing on line 916 of twitter.js

In general Digsby needs at least a pass to make sure all the API calls comply to 1.1, I know for a fact a few are using 1.0 API calls

[Brok3nHalo]

(Context: In reply to now deleted comment: "the original digsby from digsby.com used 1.0 but this has since been updated and the one I am running with the issue been patched to work with 1.1.")

(Note: Former Digsby dev, currently works at Tagged)
Kinda, the entire patch was just pointing the API calls from the 1.0 URLs to the 1.1 URLs. As far as I'm aware, none of the individual API calls were inspected to make sure their interfaces didn't change between versions and certain things were still broken even after the patch, notably reply. Really all of this should be a fairly simple upgrade for someone who has time to scan though the code for the API calls and read the corresponding API Documentation Twitter has published. I'm afraid I wont have time for a while to do it myself, but I'm right here with you, Digsby is pretty much the only way I deal with Twitter.

[Wanny]

(Bleh, deleted my previous message, I didn't read fully)

Anyone can help with this?