I've been using OAuth for more than 3 months now, about 8 hours a day during
the week while at work, using my own library and my own twitter client.
I've never had an issue with stability. Now the desktop implementation is
crappy(been posted about 50 billion times), but other than that, I've
On Thu, Jan 14, 2010 at 10:52 AM, ryan alford ryanalford...@gmail.comwrote:
I've been using OAuth for more than 3 months now, about 8 hours a day
during the week while at work, using my own library and my own twitter
client. I've never had an issue with stability. Now the desktop
I agree. I believe OAuth for mobile and the delegation between apps are the
biggest concerns that need to be addressed before the depreciation of basic
oauth in June. Both of these have been beaten to a pulp. However, these
issues certainly do not push OAuth into an unstable beta state that
On Tue, Jan 12, 2010 at 11:21 PM, Raffi Krikorian ra...@twitter.com wrote:
If that is the reason for disallowing the source param, why is this
policy not being applied uniformly? How would users of Tweetie,
Twitterrific, etc. feel if all their updates now said 'from web'? How
would the
What is the reason for no longer allowing the source parameter for
Basic Auth desktop apps?
the ability to forge the source parameter is too easy when simply using
basic auth.
--
Raffi Krikorian
Twitter Platform Team
http://twitter.com/raffi
If that is the reason for disallowing the source param, why is this
policy not being applied uniformly? How would users of Tweetie,
Twitterrific, etc. feel if all their updates now said 'from web'? How
would the developers of those apps feel?
those applications have been grandfathered in --
