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 also wonder whether this is some kind of “we accept the risk” type of situation, in which status quo will be preserved until something or someone ends up majorly breached and very publicly at one of said major cloud providers. We’re sitting on a lot of cloud-based fragility.
In the Intel case, if they aren't overprovisioning, this is only an issue with workloads that have an odd number of allocated threads (I think that's 1-"core" machines). It's possible those are a small enough fraction of their userbase they're just eating the cost.
In the case of AWS for example, they have whole ranges of machines (their t2 and t3) which wouldn’t make a lot of sense unless they are actively resource-sharing (you get “burstable CPU” power, meaning CPU shares on one machine. PaaS also. But yeah, could be cost absorption.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
