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
Spectre (esp v1) is most useful for untargeted watering hole style attacks, very often used by nation states. That one is a big danger. Meltdown (v3) is a privilege escalator, the sort of which we will see get found twice a year at minimum.
Meltdown is worse than your average privesc because it lets you tunnel right through the mitigation stack, though. Sandboxing, process separation, ASLR, it all disappears. You get physical memory reads from any random Javascript running in a browser.
Like I said earlier, this privesc is "more" than the usual because of the reduced number of steps it takes compared to our normal understanding of privilege escalation. That said, I'm not aware of any Meltdown-in-browser. Variant 1 (Spectre) is the browser risk.
There's no *public PoC* for Meltdown-in-browser but it's obviously possible. The exploit code is identical to Spectre-variant1. The only difference is you bounds-bypass all the way to kernel-space. That's it. Browsers have acknowledged the risk.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
