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
it's honestly not obvious that this is a bad idea other than in hindsight; I know I'd make the same mistake
This is like saying buffer overflows are fine as long as you overflow into data you don't care about anyway. It's basic security hygiene. Betting your security on the bug (it's a bug) not being exploitable.
that's not what I mean; it wouldn't even occur to me (before this all was disclosed) that any speculation is security-sensitive. and indeed it didn't occur to me, or to thousands of way more competent researchers that have certainly known how CPUs work since speculation existed
But it didn't occur to people... because they weren't working in both fields. The problem isn't speculation, it's speculation + side channels. HT was always dangerous, but the cache side-channels are just something nobody thought through properly.
I just hope that it’ll be possible to disable these “fixes”, because there are environments in which a local attacker is not a plausible threat. But it seems no, this’ll be shoved down our throats, and 2019 will be the first year in which processors get slower instead of faster.
think of it as herd immunity
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
