Has all to do with Twitter. Changing to OAuth was really not needed and the problems for this change really obvious in first place, but since Twitter has that much users they probably feel that they can do whatever they like. Didn't find any way to use successfully OAuth for some Linux application in two weeks, Terminal updates for sure never will work again and and and..... the list is endless. This raise the question why there is a Twitter API at all available if the usage is not user friendly at all.
Well, point is if this situation continuous for some time it may provides a way for something else that is better usable than Twitter. On Sep 4, 5:01 am, Scott Wilcox <sc...@dor.ky> wrote: > Hmm, that would be down to the developers of said applications not moving > them to OAuth, nothing to do with Twitter. They've had plenty of time and > warnings to do so. > > Don't take it out on Twitter when its down to the developers of the > applications to maintain them. > > On 3 Sep 2010, at 22:43, Herb wrote: > > > You find not one Twitter application for Linux that is working. > > Means Twitter is just useless if you use Linux. > > Not to talk from the thousands of Websites which send status messages > > to Twitter (e.g. a new posting/thread is entered). > > > Looks like OAuth really works out for Twitter. > > Thx a lot guys, but it's time to look for something else than Twitter. > > Having enough people using the service and just doing that what you > > guys have done is absolutely not amusing. > > > > smime.p7s > 5KViewDownload -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en