3 ms·
I've implemented a site before that did exactly that, because logins would be very infrequent so users were probably just forget a password anyway. It worked gr
by crazygringo 13y ago
I've implemented a site before that did exactly that, because logins would be very infrequent so users were probably just forget a password anyway. It worked great.
BUT, it would drive me nuts if I had to do that every time I logged into my bank, for example, because sometimes e-mails take 1-2 min to arrive, very occasionally even half an hour. They get queued up somewhere along the way, who knows -- maybe the spam filter's being overloaded. Sometimes your organization's e-mail simply goes down. Sometimes your webmail goes down. Heck, sometimes your e-mail gets inadvertently disabled.
If it were instantaneous, and your e-mail account always worked perfectly, then it would be great. But the way things are set up right now... this isn't a viable option for a lot of sites. And it's certainly not going to replace your e-mail password ;)
- zzzcpan 13y agoIt's viable. Just don't replace passwords with it, offer it as an alternative way to log in alongside.
- georgemcbay 13y agoI agree and would love to see this as an option on sites where full blown 2-auth validation isn't required. I wouldn't use this feature on every site but there are some sites I use infrequently enough that virtually every time I use them I have to do an email based password reset anyway, which is often implemented in a way that makes it a very clumsy version of this system anyway (since following the reset link often gives you a valid login cookie).
- yogo 13y ago...sometimes your email provider could temporarily be on some block list For the most part I consider email to be unreliable. There are simply too many things that can go wrong. I'm also amazed that there hasn't been some kind of messaging protocol to replace the damn thing (throw it on top of http even). I guess spam really ruined it for everyone.
- betterunix 13y agoThe reason email has not been replaced is that it is just too versatile. The message format is simple, the relevant protocols are ubiquitous, and most people can understand the interface they are presented with when they use email (enter an address, enter some text, optionally attach a file -- it's dead easy). Sure, using email as an authentication system is like using a knife as a hammer, but it gets the job done when you do not have time to grab a better tool.
- yogo 13y agoWhen I say replace email I don't mean what the end user sees but the protocols. I think a POST request would work great. I'm sure there has been conversation surrounding doing something like this, and it surely doesn't solve the problem of spam but I'm able to see much more interesting things surrounding online communication.
- chewxy 13y agoI found my experience with Fork the Cookbook[0] the same as well. Also, add to the fact that this is a novel method, I get a lot of emails asking why they get new passwords everytime. If I were to rewrite FtC today, I'd go with Persona. [0] http://forkthecookbook.com http://forkthecookbook.com
- duck 13y agoWell, the OP didn't say this, but what really would be great is to extend it to SMS as well. In most cases that would solve the delay piece.
- ohazi 13y agoIn my experience, SMS can have longer and more frequent delays than email.
- bradleyland 13y ago> "sometimes e-mails take 1-2 min to arrive, very occasionally even half an hour" That's because SMTP (the protocol that moves email around) doesn't guarantee delivery in any specific time period. Many MTAs (message transfer agents) are configured by default use retry intervals measured in minutes, not seconds. Relying on email for authentication means asking your users to wait minutes, not seconds, and asking users to wait minutes to get logged in to your website is horrible usability.
- __--__ 13y agoIsn't this also horribly insecure? Unless it's encrypted (ha. ha.) anybody can intercept the email and get access to your account.