this post was submitted on 13 Nov 2026
1147 points (97.2% liked)
Programmer Humor
34196 readers
826 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
2FA is a good thing. You don't want it to go away.
I don't think the 2FA is the issue this comic is attempting to convey.
Except that it needs another jump for autofill 2fa
2FA on the login form is a thing for some sites,
Except when it's just an email, or worse, a txt message, or worse, a whatsapp message, with no other option for using a proper 2fa generator...
But also, not every site needs 2fa, sometimes I really couldn't care less if someone managed to hack into something, because I can just make a new account if that happened...
What really bugs me is that TOTP is objectively easier than any other form of 2fa. Just import the library, add the field on your login form, and you're done.
Any company that chooses SMS or email verification over TOTP emphatically does not know what they're doing.
2fa by email is probably slightly easier than TOTP, if the account verification via email is already implemented, but yeah, it's not like it's significantly easier...
That is a fair point. But again, you probably have to implement TOTP or something like it anyway, to generate the code.
They know: they're selling your data. They don't mind about your security
But all of those data points are "cheap." They already ask for email; I haven't signed up for a service that didn't require an email address in...thirty-ish years? Phone numbers are easily available on the dark web and essentially worthless to data brokers. A connection to WhatsApp would get you almost nothing, since Meta's already sucking up all of that data. The custom app is the most potentially lucrative of those methods from a data perspective, but it's also undoubtedly the costliest, which is why you see it the least often; you have to evaluate the ROI, and that algorithm is never favorable.
They don't care about your security, that much is beyond doubt. And as a result nobody has updated that code since before TOTP was adopted, which I think is the real reason.
Well, you have a point, I have to admit. 🤝
The real reason is conversion. The majority of users aren't good at technology, so you risk them losing their TOTP secret. Then the user either just says "screw this site" and leaves, or they take time getting customer support to reset their key.
So depending on the branch and customer base, it can often be much "cheaper" in the end to send login codes via email instead of using TOTP.
Maybe. And I think that could make sense as the PM's answer, but I also think that a TOTP app is starting to become mainstream enough that it's not a huge deal.
You don't have to implement totp for these alternatives... The "thing" about totp is that there's a shared secret and a timestamp. Due to potential drift in clocks you need a window and period to know how many time steps to test, and how long each is.
But with an email/SMS/WhatsApp, there's no shared secret. So you can simply send a random code, and store server side when it was generated. Totp makes no sense in that case.
Not that totp is difficult to implement at all. My implementation for work was what, less than 200 lines of C++ I think? I didn't implement the sha1 myself though.
You do have to implement TOTP, just not necessarily RFC 6238. Time-based one-time passwords require a shared secret, a shared time and a time-to-live. The shared secret is usually the key for generating the code, but can be the code itself. The shared time is still needed in mail authentication between the code generator and the code validator. The thing that's usually different is the time to live, but in RFC 6238 it is a parameter, so you can implement mail verification with it and a long TTL.
An earlier version of that comment said "something like TOTP," but I guess I left that out while I was revising it. My point is you have to implement something that does most of what TOTP does anyway, so why not just use the version that's already been stress tested?
A local marketplace service in brazil only allows me to login using whatsapp codes or sms. When i enter the passowrd they ask for a whatsapp code
I don't want it for like 95% of the logins I have.
Seriously. Why would i care if someone logs into most of them. What are they going to do watch a movie on my Netflix account, play my kids roblox games, or change my crew on my Rockstar account? It's unnecessary bs.
The bigger issue is gaining account details and personal info for identity theft.
Which also doesn't matter anymore because companies sell our data all the time or just give it away through their own data insecurities. Or yanno, white pages. com and similar exists and its pretty easy to find anything about anyone anytime.
They don't sell your ID or credit card information though, which is information a lot of these kinds of services have.
Who cares if someone steals your identity? Just go on the dark web and buy a new one.
Any account that does payment (like your netflix one), will be used to test out stolen credit cards. This will in turn flag your account for fraud. You might not want that. Unless you do, I don't know
It's not about a specific account, it's about compromising your info.
The info one company considers enough to verify you when you call or chat with customer service, another company will give out freely. They can then hop and skip through those to get access to one of your accounts they actually want.
Your entire online security is only as secure as your most insecure account.
I get the theory, but if it itself relies on some login-based service (like email) it becomes a kind of chicken and egg problem.
My work 2fa can go away. I don't give two shits if everything in the work app is printed in global papers, just stop making me go through a 5 step process to see my fucking roster.
Almost all sites should allow me to choose whether I want 2fac. And they shouldn't prompt for it nearly as often as they do - some services do it for every login, most seem to do it every month at least.