3 ms·
Well Twitter only has 2 modes, public and protected. An app can access anything public through the existing API anyway without authentication. The only differ
by sh1mmer 18y ago
Well Twitter only has 2 modes, public and protected.
An app can access anything public through the existing API anyway without authentication.
The only difference here is that you can allow apps your trust to access your private data (or functions, like sending tweets) without giving out your password. As such it's a big step in the right direction.
Twitter apps have been one of the worst offenders for the username/password anti-pattern because of Twitter's use of HTTP-Auth for the API.
- amichail 18y agoThere are benefits to having the mode I describe: * your app can perform more API calls without IP-based rate limiting (which can be a real problem when using the Google App Engine due to shared IPs between apps) * you can be sure that the user is who he/she claims to be (without a DM hack), which is important for some apps
- amichail 18y agoNot sure why parent was upmoded. Is there a reason why one would not want this mode added?