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
Basically it seems their engineering teams have, until now, considered it acceptable to have known-to-fault instructions operate on *complete garbage*, ignoring *all* privilege rules, as long as they will never retire.
This is, of course, completely insane from a security perspective, and given that we're now acutely aware of speculation attacks, represents *many* different opportunities for leakage. L1TF and ZombieLoad are on a completely different class from Spectre/Meltdown.
So my recommendation at this point would be to avoid Intel CPUs for several years if you care about this sort of thing, and OSes *need* to implement hyperthread pair privilege boundary separation, since that's most of the attack surface.
gotta keep the single-threaded performance train going no matter what, I guess?
Yeah, this is literally another case of "let's save ourselves a bank of AND gates to return 0 on faults".
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
