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
oh i had assumed meltdown and spectre were fundamentally similar because everyone writing about them is lumping them together.
All three problems involve speculative execution. They could've all been grouped under one umbrella name referencing that, though that wouldn't be as useful. That category is then broken down into specific problems. A blatant CPU bug, a not-so-obvious CPU bug, and a mess.
Variant 1 ("Spectre") is the mess (direct branch misprediction), Variant 2 ("Spectre" again, whyyy) is the misprediction training thing (fixable CPU bug), Variant 2 ("Meltdown") is the reading RAM from the kernel thing (fixable, blatant Intel bug).
To somewhat further confuse things, you can combine Variant 1 and Variant 3 into the same exploit to do things like read kernel RAM from Javascript. Then you're leveraging both issues at the same time (they fit together nicely).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
