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
Completely protecting against this simply requires being able to roll back *every* effect of a bad speculation. Have a few extra cache lines, extra branch predictor counters, that are discarded if the speculation fails, but become the real ones on success. Stall if you run out.
That's just the easy stuff, but nowhere near sufficient to completely protect against speculation attacks. You also must not speculate at all on anything that effects any resource that is shared with another compute thread. No main memory access, no shared caches, ...
... no hyper-threading (because then everything would be shared), no sharing of FPUs etc between cores, and so on. Because roll back isn't helping you if another thread can already see the speculation while it is happening.
But nobody knows how to generate an exhaustive list of all relevant side channels and when nobody knows how to generate such an exhaustive list then nobody knows how to build a secure processor that speculates.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
