You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
This isn't a chip attack, it's a stupid design bug. That said, there *is* a difference in design philosophy. Intel has chosen performance over any kind of design sanity / safety, every time, it seems as a systematic rule. AMD hasn't.
So while both AMD and Intel have been equally hit by the general idea of speculation-based leaks in userland code (nothing the CPU can do about that), Intel has also had a huge pile of massively privilege-crossing speculation leaks that AMD hasn't.
Because the Intel philosophy seems to have been "ignore security/sanity until the instruction retires", so all kinds of batshit insane stuff happens in speculation on Intel CPUs (like bypassing guest VM page tables or loading bad or privileged data) which doesn't on AMD.
Thanks! Just wasn't sure if AMD was actually more secure or if it was about who people tried to attack more.
But AMD and Intel weren't "equally" hit. Meltdown wasn't possible at all on AMD bc of their design. AMD has shown what it means to perform under the actual pressure of competition; they are more conscientious. Intel took shortcuts, cooked benchmarks and even threatened PC makers
"speculation-based leaks in userland code" = Spectre v1. "massively privilege-crossing speculation leaks" = Meltdown (and L1TF and others).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
