I don't think it is. I recommend using a password manager that supports hardware 2fa. One of the main issues with the proposed paper mechanism are that it doesn't support rotating passwords individually. Another is sites that share second and third characters would share a password.
Please understand that this "company" and "CEO" are most likely a teen skiddie. I doubt they care about vulnerabilities in their software and I'm not sure if their users would know about them either.
It looks to be very relevant. CRLs are more frequently checked now due to bandwidth and compute becoming much cheaper. OCSP is a common solution for larger CAs. Cross-signing is becoming more common, and it still is a mess with clients validating it in different ways. Let's Encrypt used cross-signing when they rolled over to their own ISRG X1 root. There's a CA/Browser Forum group which defines rules and standards for browsers to trust public CAs and all major browsers use them to determine which roots to trust. Certificate Transparency logs are also a new development which is like a blockchain of issued certificates. CA/B Forum requires CT to be implemented by all publicly trusted CAs.
The classic tetris scene has been crazy lately. Rolling (the name of the new strategy) allows players to easily play past the "kill"screen of level 29. Classic tetris matches are becoming endurance matches and we're seeing new records broken left and right of highest score and highest level in both PAL and NTSC versions. For Classic Tetris World Championships they're considering adding a second killscreen by editing the rom to limit the length of matches.
As an aside, check out the 30 minute documentary "Farewell Etaoin Shrdlu" (https://www.youtube.com/watch?v=1MGjFKs9bnU) about the end of the linotype era. I'm amazed at the engineering that went into linotype printing.
My team started development of a React SPA. It was initially written with jsx. As we're starting to implement more, I'm finding more and more cases where the js code was wrong; property names that don't exist, wrong types being passed around, and non-existent props being used.
How do you suggest addressing this in a 10 dev team when developing in js?
Check out the history of Wind Waker's barrier skip as well. I believe it saves 30 minutes of a 3.5 hour run. It's always been known that finding a way to skip Wind Waker's barrier would be massive, but it resisted any attempts to bypass it until a year ago. The barrier blocks off the final dungeon of the game.
Usually external tools like this wouldn't be allowed, but the community decided on allowing it because the minigame is so brutal. It's pure RNG and I've seen runs lose 15 minutes to it. This tool removes the random element from it and makes the total run time better reflect a player's skill rather than just their luck.
The problem that I see is that the child had no choice in the matter. Imagine if you turned 21 and were kicked out of the country that you grew up in and had to move to a country that you haven't been to since you were a baby. I don't really know what a reasonable solution to this might look like.