4 ms·
Ok, So; I posted on monday about mytwitternotebook, an app I made. Originally, I made it so that you signed up with an openID, and then put in your twitter use
by izak30 18y ago
Ok, So; I posted on monday about mytwitternotebook, an app I made.
Originally, I made it so that you signed up with an openID, and then put in your twitter username, and then got a verification DM, and then verified.
_Nobody_ understood it.
I switched to using twitter username and password, and nearly instantly, my user-base doubled.
I don't store the UN or PW at all, ever; I verify with the twitter server, and forget about it, you don't even need to put your UN or PW into my site to use my service, ever, it can be done completely by Direct Message.
It may be stupid to share your password, but it's stupid to use the same password everywhere. Turns out, it may be stupid, but it's easy, and you get good results.
- thwarted 18y agoIt's not so much a matter of password exposure for people who share passwords with other sites (that is their own fault), it's having to trust all these sites you put your password into to keep it secure (you may claim you're not storing it, but how can I verify that). The risk of your twitter password getting out is impersonation and taking control of your twitter account, with no way to recover it. Remote keys have problems too, but the idea behind remote keys is that you enable third party access to the core functionality but the authentication and control of the account itself is out of reach of the third party.