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
From what I've seen (I'm still reading the Google writeup, so not 100% up-to-date) you could just as easily say that OS makers have been fucking up for 20 years with the way they do page mappings.
Eh, nah. Meltdown is entirely Intel's (and ARM's) fault. There's no excuse for that one. OS makers aren't at fault. Chips took an ugly shortcut and it backfired badly.
Spectre is more fun. The BTI attack is still a chip flaw, but you can forgive them for not thinking about it. That one is fixable. The real fun one is the misprediction/speculation attack. That one is fundamental. It affects how we think of secure coding.
I speculate (ha ha) that speculative execution barriers will become architectural and will be exported as compiler intrisics and we'll teach about them like we do for concurrency barriers and atomics for multithreading. There's just no easy magic fix.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
