Jesse Stay wrote: > > Thanks for being open about it Alex - it helps us plan better, and it's > comforting to know it is a priority.
Dude, the only priority it has is LOW. Did you an I read different emails? Alex wrote: "If we can deliver it sooner with minimal effort, though, we will." Basically, this is a "ain't gonna happen" response - because it seems nothing at Twitter which ought to be simple or minimal in effort seems to work right the first time. Or the second time. Or how many times have they "switched their stack" so far? I really appreciate Alex's efforts here, but lets call a spade a spade: OAuth won't happen until Twitter has to shut down the service when someone steals 50% of the user's passwords through some poorly written API-using app that gets pwnt. Then, Twitter will simply shut off the API. And won't turn it back on until they have some kind of API key implementation in place. Then, they'll quietly change their ToS to say "sharing your auth credentials is forbidden". It could be a long wait ... -- Dossy Shiobara | [EMAIL PROTECTED] | http://dossy.org/ Panoptic Computer Network | http://panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70)
