I totally agree... Ivo, I got the same answers for a pretty similar
question some months ago...
I do not see the link between the source parameter and how the
authentication is made...
Cheers!
Ivo wrote:
Hi,
short answer: oauth is for delegated authentication; I'm using direct
It's an incentive to move to OAuth.
Twitter has made their intentions clear about Basic Auth: They want it
to go away. By restricting the source parameter to OAuth requests,
they give developers an incentive to move forward.
On Sep 15, 4:20 am, Emrah e...@ekanet.net wrote:
I totally agree...
Ok, but againplease make OAuth pages at twitter mobile friendly so
that the mobile web sites can use it!
On Sep 15, 11:28 am, Duane Roelands duane.roela...@gmail.com wrote:
It's an incentive to move to OAuth.
Twitter has made their intentions clear about Basic Auth: They want it
to go
With all the freely available examples, and all the freely available
documentation and support available through oauth.net, what's stopping
you from cranking out an OAuth client implementation in 2 hours?
OAuth helps prevent, or at least make obvious for the time being,
spammers. HTTP Basic Auth
Hi,
short answer: oauth is for delegated authentication; I'm using direct
authentication of my own account. Both are valid use cases, so in my
opinion the source parameter should continue to work for the second
use case (I can't find a good reason to only support it for delegated
authentication)
