3 ms·
Here's a random idea: I wonder if the "one password" paradigm is the problem. What if Twitter (and any other web service) could have multiple passwords per us
by sanj 18y ago
Here's a random idea:
I wonder if the "one password" paradigm is the problem. What if Twitter (and any other web service) could have multiple passwords per user. Now you can give away a password at will to whatever Twitter service you want. When you don't want it to be used anymore, just delete it.
Much simpler than OAuth!
- cgranade 18y agoThat's similar to, but more sophisticated, than what FriendFeed does. FF has an "API password" that you plug into other sites, and you can change the API password at any time, but they don't have separate API passwords for different sites. If there's a rogue site abusing your account, then you have to revoke all sites.
- spoondan 18y agoSimpler for whom? The user who has to manage N passwords for N services, instead of one password? I'd rather Twitter's staff suffer a moderate amount of pain once than have every user suffer lesser pains continuously. Programmers (myself included) too often fail to consider whether "technically simpler" is "actually simpler". It is one of the things that ensures the poor quality of software. We'd do well to understand that our job is, first and foremost, to make life easier for the people using our software. This may require martyrdom from time to time. Besides, OAuth isn't all that complicated. Distilled, it's similar to your idea but with several additional benefits, not the least of which is that there are existing implementations to help you on your path.