Because Twitter would require keys, not usernames and passwords.
Logons go to Twitter, and keys are returned. Programs would (will)
break unless grandfathered, but that's a manageable issue.
That said, there should be a way for developers to use Basic Auth to
"hash out" (develop) their code for eventual oAuth implementations. It
is too useful for developers to do initial coding (or at leasat some
coding) in Basic Auth, and then tweak and package it for oAuth, as I
On Dec 9, 9:24 pm, "Dean Collins" <d...@cognation.net> wrote:
> How are they going to stop basic auth?
> If a website already have the username/passwords doesn't that mean they
> can log in on a users behalf until they change the password via the
> twitter.com website?
> -----Original Message-----
> From: email@example.com
> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of Patrick
> Sent: Wednesday, December 09, 2009 9:12 AM
> To: firstname.lastname@example.org
> Subject: [twitter-dev] Basic Auth deprecation coming
> With Basic Auth deprecation coming in June 2010, will developers have
> a "sand box" way to use Basic Auth? I mean, it's handy to develop and
> understand code with Basic Auth, and then cut it over to oAuth. Any
> ideas?- Hide quoted text -
> - Show quoted text -