OAuth has benefits all around for everybody. In addition to the
benefits already mentioned:

1) For a web app like mine, it saves a TON of support workload with
people who change their Twitter password, don't change it in my
system, and then blame my system for not working because it's not able
to access their Twitter account.

2) If your app has its own API, you'll quickly understand the need for
OAuth and some form of control over the services that access your API.
I just haven't had the time to put an OAuth server on my own API (have
been too busy taking down my Christmas decorations these past week or
three), but it's coming. You really get annoyed when spammers cram
their crap into your system via ip-hopping proxies, and there's very
little you can do about it apart from finding the shit and deleting it
afterwards.


-- 
To unsubscribe, reply using "remove me" as the subject.

Reply via email to