Earlier quoted context omitted.
4. Email delivery period. Using AWS Simple Email Service, you're actually sharing an email server IP address with other accounts. At times those accounts can get the IP address added to spam lists. All the sudden your emails stop getting received on some clients.* * Solution to this is to pay $$ / month to get a dedicated IP address, then never let it get added to a spam list.
Dedicated IPs aren’t great because they’re completely untrusted. Better to sign up with a smaller email provider than mailgun/ses
Ask HN: Why aren't one-time sign in links more popular for authentication?
101–110 of 198 posts
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#102We have tried this for a while and the following reasons made us kill it: 1. Email delivery latency: depending on the service you use, the time it takes to deliver emails to the user can vary. Worst case I encountered was up to 20 minutes delay when there were issues with Mailgun. 2. Usability: you have to leave your current app and switch to your mail client. You may be on a device where you don't have a mail client…
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#103Earlier quoted context omitted.
I meant my first comment in jest. I will consider your advice, but I imagine switching from one password manager to another will only certify me as a genuine and eternal password hater. (Also, a password stored in a password manager is something you have, not something you know, so it's completely inconsistent with the principle of MFA. I mean, the reasons to hate passwords just increase as long as I think about it.…
There is another option if you wish to adhere to the principle of "something I know" and that's to generate a base64 key. eg SITE="www.example.com" SALT="passphrase" printf "${SALT}${SITE}" | shasum -a 512 | base64 | cut -c -25 (Though you're better off using some online tool that converts SHA 512 to base64 directly since the example above converts the ASCII string of a hex representation of the SHA 512 hash into bas…
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#104Earlier quoted context omitted.
>sign up/sign in Why were clear terms like login/register/logout replaced with a “sign ...”? I get confused twice a week by these, especially because the difference between “in” and “up” is so subtle (and overloaded, like “sign up for a meeting at friday”, unrelated to registration routine). Sorry for offtopic, but it is really annoying. Is it more linguistically correct or just a hipster thing?
I researched this several years ago and for various reasons it's best to use: sign up, log in, and log out.
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#105Earlier quoted context omitted.
I've experienced that too.
Then you haven't used it for very long. Besides that, more exists than some tech giant's gambit to gather and exploit as much user information as they can. Nobody should use gmail, unless they are forced to by their job (in which case they should try to change it if they are in a position to).
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#106Oh, this is so terrible. I hate this approach with a passion. E-mail is NOT INSTANTANEOUS. It was never meant to be. It happens to arrive quickly for most people most of the time, but you should never, ever, base a service on that. Many systems have greylisting in place: a new sender gets a 4xx reply, and is allowed through only on subsequent retries after a pre-set time period. This is often as much as 30-60 minutes…
Email has been nearly instantaneous for me for the past decade or so. Either it arrives in a 30 second window, or never. Usually 2-5 seconds.
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#107Oh, this is so terrible. I hate this approach with a passion. E-mail is NOT INSTANTANEOUS. It was never meant to be. It happens to arrive quickly for most people most of the time, but you should never, ever, base a service on that. Many systems have greylisting in place: a new sender gets a 4xx reply, and is allowed through only on subsequent retries after a pre-set time period. This is often as much as 30-60 minutes…
Email has been nearly instantaneous for me for the past decade or so. Either it arrives in a 30 second window, or never. Usually 2-5 seconds.
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#108Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#109Earlier quoted context omitted.
Why can all instant messengers do this “instant” part and email cannot? I’m aware of mta chains, decentralization, etc, but heck.
Because, as jwr says, it was never meant to be. The mental model is that of regular mail that gets collected at post offices, then split by major destination, sent on, and finally ends up in a mailbox. Mail servers do not even have to be on the internet ( https://en.wikipedia.org/wiki/Non-Internet_email_address ), or on a network at all. It was fairly normal to have a time sharing system dial in to a mail server ever…
Re: Ask HN: Why aren't one-time sign in links more popular for authentication?
#110How about scan QR code on login screen by authenticated APP on phone. Many companies in China use this way. does there have any possible exploit/disadvantage of this method?
* requires app: This is the main killer. I'm not going to install some random SaaS vendor's app on my phone just so I can log in
* requires internet access on phone: sucks if your phone doesn't data, cell reception is spotty, or wifi isn't set up
* less phishing resistance: one time sign in links are impossible to phish, and passwords have mitigations that protect against phishing (eg. password managers that only auto-fill on the correct domain) and users are generally aware to "check the address bar before entering password". scanning a QR code has neither of these.