Leveling the playing field is elephant in the room easy:
Immediately ignore the source parameter on all Basic Auth calls. Right
now. It's a 5-second coding job.
If Tweetie, TweetDeck, et al want their app name back in the tweets,
sure, they can have it by all means. As soon as they've converted
Actually, we'll know the answers at Chirp or before. Chirp is the
watershed for Twitter and the developer ecosystem. Time as we know it
will be reckoned B.C. (Before Chirp) and A.D. (After Disclosures). ;-)
On Tue, Feb 2, 2010 at 9:16 AM, Isaiah Carew isa...@me.com wrote:
Leveling the playing
How so? What do you think will be the significance of chirp for desktop OAuth?
Was there an announcement that I missed?
isaiah
http://twitter.com/isaiah
On Feb 2, 2010, at 10:30 AM, M. Edward (Ed) Borasky wrote:
Actually, we'll know the answers at Chirp or before. Chirp is the
watershed
There's a whole chunk of the hacking session devoted to oAuth.
On Tue, Feb 2, 2010 at 10:49 AM, Isaiah Carew isa...@me.com wrote:
How so? What do you think will be the significance of chirp for desktop
OAuth? Was there an announcement that I missed?
isaiah
http://twitter.com/isaiah
On Feb
Aral,
Not sure how in-depth you've been following developments and
announcements of the Twitter API, but come this June you will have no
choice but to put ScotchGuard on your Ferrari's seats. In other words,
come June timeframe, usage of OAuth will become mandatory and Basic
Auth will be
Thanks for the additional info, Dewald, I appreciate it. I haven't been
following very closely since my app only really uses a tiny bit of the
Twitter API.
From the recent @twitterapi tweets, it's clear that Twitter is working on
oAuth WRAP (which is a great step forward) and I'm sure they're
(And, of course, I meant to write Ev Williams is – way to make a
poignant closing remark!) :P
