1,162 karma · joined May 24, 2010
Then tried signing in. "Enter the passcode that was sent to <email>." Fail 2 - no passcode was ever sent. (Yes, I tried the resend button multiple times, because I'm not a moron. Yes, I checked my spam folder, because I'm not a moron. I know the HN crowd would have taken great pleasure in explaining the obvious to me if I hadn't mentioned it.)
Even if that had worked, how is copying a code from unencrypted email supposed to be either easier or more secure than a password? Fail 3.
FTFY
For tools that can identify where the bottlenecks are, I recommend watching Emery Berger's talk "Performance Matters" from CppCon 2020 (either of the two links below should work). He introduces some innovative new profiling tools for this sort of analysis.
(2) Once Microsoft work enough of the bugs out, which I'm guessing will take another 2-3 years, I suspect Windows on ARM will be the Next Big Thing, or at least one of the Big Next-ish Things. ARM supplanting Intel will be a general Thing.
A couple of other issues:
- The linking procedure is poorly explained. It took me a while to figure out what you wanted me to do. (Maybe I still got it wrong.) Showing devices in Finder is a feature most people have probably never heard about - who has any reason to physically plug a device into a Mac these days? I had never seen that screen before.
- I suspect you only tested this on laptops, because it tries to show the battery status of my desktop iMac and reports "Battery 0% Power Source: Unknown" :)
If the subtransaction is later rolled back, this is starting to sound like the kind of speculative execution information leak that led to the Spectre attack. I wonder if you could base a similar attack on this?
A forkbomb implemented in hardware.
(1) There's no evidence of anything wrong with AMD's RNG.
(2) Lots of people on Github and HN don't understand the birthday paradox.
Today in "Unexpected WH40K quotes"...