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
If this is what it is, then in my book it's not a new flaw, just an instance of Variant 1. I never considered the cache to be the only side channel available. Pretty sure I mentioned DIV and execution unit timing at some point.https://twitter.com/11rcombs/status/954069852062396416 …
This is why I keep saying Variant 1 (which I call MISPREDICT) is a pervasive problem that requires changing the way we teach CS to fix, not something you can fix in the compiler like MS seem to think you can.
I mentioned this alternate side channel here.https://github.com/marcan/speculation-bugs/pull/2#issuecomment-355904408 …
Added a note about alternate side channels to the doc: https://github.com/marcan/speculation-bugs/blob/master/README.md#alternate-side-channels …
I wonder if it'd be possible to disable all non-constant-time operations (incl. loads) in speculatively-executed code, and if the perf hit would be small enough to be worthwhile
(which I see you touched on in a GHI comment)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
