|
|
|
|
|
by cxr
474 days ago
|
|
Those passkeys that you and GitHub are talking about require a separate authenticator to use. > no "forced 2FA workflow" What does "2FA" stand for? > it's easier than logging into HN You have your thumb on the scale (which seems to happen every time someone criticizes GitHub). You have already indicated a willingness/desire to use an authenticator. At that point, there is literally nothing stopping the authenticator from providing the exact same user experience, where instead of releasing your "passkey", it provides your password to HN's login form. And oh wait that's exactly how scores of password managers work, including the ones that are built in to every mainstream browser. (If you're somehow using one that for whatever reason doesn't do that, then it's self-inflicted, which is exactly opposite to the case of the forced 2FA flow that GitHub imposes.) This is without even mentioning that you have to set all this up. |
|
Two factor authentication, I'm sure you can google it.
> The passkeys that you (and GitHub) are talking about require a separate authenticator to use.
I'm not using anything other than my browser.
> You have already indicated a willingness and desire to use an authenticator
I'm only using my browser, it was 1 click.
> This is all before we even mention that you have to set all this up.
Yeah, once (which doesn't take longer than 15-20s), just like registering on HN, you do it once.
Also as I stated it's my opinion, having a different opinion doesn't make me dishonest