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 mean this in all sincerity - why is this a problem?
Because now you're broadcasting extremely sensitive data (as in: all your private keys are belong to us) intended for one core to all cores. That breaks down the core isolation boundary, making the security as weak as hyperthread isolation. And we know that one is really weak.
It's been this story time and time and time again. Intel CPUs have *no* security boundaries in speculation. Their only security boundary is instruction retirement. They have zero compartmentalization or defense in depth. It's insane.
Like, this is the moral equivalent of running your web Javascript VM interpreter in kernel mode - no, better, inside the hypervisor outside the guest running Chrome, because surely it has no bugs and why would you ever need any other security layers or defense mechanisms?
I'm not an CPU architecture expert but even to me the idea of sharing R/W resources across cores like this sounds bad.
Large shared caches are a big factor in modern performance improvements for many years, it’s an unavoidable situation now that we’re hitting a hard wall on core frequencies. It just needs to be implemented carefully which Intel did not do
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
