Yup, ≠ is right “under” =. As is ≈.

My commits are a little too specific to post here, lmao. I likely put too much info into them, I’m still trying to get a good balance.

I mean, it got 5 full seasons. It wasn’t terrible by any means.

Facial recognition isn’t really the same thing. It’s not trying to interpret an image into anything, it’s being used to compare an image with preexisting image data.

If they are using something that understands text, they are already doing it wrong.

Absolutely. Sometimes firing your customer is the best option for everyone.

Jquery is still extremely relevant. React exists as well, and is also a good framework. I just happened to think of jquery first.

No? How is that the logical conclusion? You need to understand any language, and any quirk of that language, in order to effectively write in it. JavaScript is powerful, and moving farther every iteration. Strong typing is just not something it takes into consideration. In the same way that C# doesn’t take white space into consideration, and python doesn’t terminate its instructions with semicolons.

Each language is different, each language has its own quirks that you need to understand and get used to. If that wasn’t the case, we would have one objectively “perfect” programming language to use in all situations, on all machines, for every use case.

Write your business critical process in brainfuck and have job security for life.

The typing system is just a “quirk”. As long as you understand the (admittedly annoying) exceptions to the way your brain expects typing to work, everything works quite well.

And tbh, transpiled TypeScript libraries can be called from JavaScript as if it was JavaScript… because it is JavaScript. There’s no need to worry about typing unless you’re doing something like passing a string into a function that expects an int, and you’d run into those same problems if the function was originally JavaScript.

Edit: a word

If only it was intentional…

Hey now, CSS is just C with some extra S’s. Just rip off those S’s and you’re styling in C.

Both are fine tbh. Javascript has come a long way from a decade ago, and mixing in a decent framework like jquery does wonders.

You’re misunderstanding. Totp apps require authentication to use them, be it a password or bio-authentication. SMS does not, it just requires the phone number.

You can get the phone number through any number of ways, but it can be done remotely meaning no one ever interacts with you or your phone. Through various methods, they have your phone number transferred to a different phone, and then have the SMS sent directly to them.

Totp apps (typically) have a backup system in place. 1password as an example, uses their servers to host the data. But you can also back that up. The chances of someone gaining unauthorized access to your Totp account comes down to your security, and which service is chosen. 1password again as an example, is fully encrypted, they can’t see your passwords, if you forget your security token, the only solution is to wipe the entire password store and start again.

The difference in security is mountainous. It’s the difference between a single family home, and a bank vault.

Poorly secured keys usually still require device access, unless they are secured so poorly that the individual would be compromised in one of many other ways regardless.

Stealing a phone number requires, at most, paying off an employee at a telco company. At best it just requires a call and some social engineering. And don’t forget, people who leave their phone laying around without a passcode exist.

Now, neither of these are really options for a dragnet approach, they’d need to be targeted. But the fact that one can be done fully remote should be a red flag.

I don’t believe I’ve run into that, but yeah it completely misses the point of totp. Hell, I’d prefer a lockout over SMS backup in most cases, my totp authentication has multiple encrypted backups.

Why?

Totp is easier, cheaper, and more secure. It makes no sense to go with SMS.

It absolutely is, the issue is that most mfa apps spit out 6 character outputs, while Steam requires 5. They’d need to implement the alternative algorithm, but 1password for instance flat out refuses since it’s non standard.

SMS isn’t even secure. Mitm, social engineering, straight up theft, and more are all ways around it. It should never have been implemented, but especially not when totp exists.

To be fair, those are less a nav bar and more contextual content. You likely also have the main nav bar along the top.

Mmm I don’t think this could be JavaScript. Unless we are always returning true.