I'm curious to post this question to see if Twitter has fully thought
out the impact of forcing OAuth onto their API applications.  While it
may appear to be a more secure method preferred in principle by users,
the fact of the matter is that one of the main benefits of the API, is
the ability for third party twitter alternatives to be created, thus
allowing people to tweet during "business hours", when they normally
could not due to firewall / web sense restrictions, etc, that prevent
them from accessing the twitter.com domain.

Via basic authentication, users would never have to visit twitter.com
to login and gain access to twitter functionality via api clients.  By
shutting this down, you are now forcing ALL potential users to login
via twitter.com, many of which do not have access to this domain in
their workplace environment, thus excluding them from easily using
your service wholesale.

This can / will, I suspect, have significant impact on twitter usage /
volume, unless I am missing something and there is an alternative the
does not require them to directly access the twitter.com domain to
grant access.

Reply via email to