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
I just hope that it’ll be possible to disable these “fixes”, because there are environments in which a local attacker is not a plausible threat. But it seems no, this’ll be shoved down our throats, and 2019 will be the first year in which processors get slower instead of faster.
Some of the fixes have negligible impact. Those are always on. Some don't. Those are controlled by kernel commandline parameters. See Documentation/admin-guide/kernel-parameters.txt (grep for spectre_v2 and spec_store_bypass_disable and pti)
But really, the cases in which you want these things off are pretty limited. Most of this stuff hurts performance on context changes (cross-process and cross-VM), and workloads bounded by that are... more often than not people serving stuff over the internet.
Also, some of these bugs are exploitable remotely. With shitty throughput, but you don't need much throughput to steal an encryption key. I already predicted this earlier this year (hard but not impossible) and well, people found a way: https://www.zdnet.com/article/new-spectre-attack-can-remotely-steal-secrets-researchers-say/ …
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
