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
Aaand suddently VM-exit latencies on Intel CPUs will go through the roof, oh, and if you're still putting different guests on sibling hyperthreads you're going to get pwned and you know it. Good job, Intel. You saved a few AND gates. Was it worth it? https://www.redhat.com/en/blog/understanding-l1-terminal-fault-aka-foreshadow-what-you-need-know …
This speculation saga just keeps getting worse and worse, which goes on to show that there's a huge disconnect between CPU designers and security researchers. This is the CPU equivalent of foo = bar[untrusted]; if (untrusted > bound) return 0; do_stuff(foo);. Who does that?!
"Let's use garbage bits for something, it's fine, we'll throw away the result later". No. No it isn't fine. Why the fuck would that ever be a good idea? If you can't take the fault immediately at least poison the garbage data with zeroes!
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
