I told you so. https://github.com/marcan/speculation-bugs#future-speculation …https://twitter.com/andywingo/status/1097418315570577408 …
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
(And don't get me started on terrible ideas like eBPF JIT in the kernel)
Speculation is something you can plausibly deal with in security-critical code (e.g. file parsers) with *very* careful use of barriers and such (and it's *hard*). But JITs? Yeah, no, you're screwed. You need process isolation (and that still has side channels).
What I’m curious about is when someone will break CloudFlare Workers, which runs everyone’s workers in the same V8 process, but disables timers entirely - so you’d have to rely on externally observed timing of HTTP requests etc. I think it’s doable.
are there _any_ available (modern) CPUs that don't have these problems yet
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.