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
4/ Problems (3): - disk throughput can be throttled (GP2, IO1) - if you use SSDs on cloud, which model do you have, are you the only writer?, how to get a proper RAID setup?, ... - how to minimize the number of switches between your instances? - unpredictable network behaviors
5/
Problems (4):
- reliable UDP multicast: AWS seems not to support UDP multicast, while GC does not. Anyway what's the expected packet loss?
- security: spectre attacks, data hosted on 3rd party, ...
- #crypto is growing. When next bull run? How to ensure 10x/100x scalability
6/
Path to metal 
Our infra team has outstanding experience in secure, god wrath resistant, deployments, so we discussed a lot about pros and cons.
Here are the 2 cons summarized:
- hardware decay
- physical hosts maintenance (trips to datacenter, hardware expertise, ...)
7/
Benefit (1):
- the entire infra behavior is predictable
- RAID enabled historical sharded data-warehouses kick asses
- KYD, KYM and KYC 
: Know Your Disk, Know your Mem and Know Your CPU
- dedicated switches and firewalls, back to back connectivity for core servers
8/ Benefit (2): - reliable UDP multicast - bare-metal Linux installs - you're the only one using your CPU (see spectre-like attacks) - colocation services offering
Finally somebody with clout is telling everyone what cloud providers never mention. This does however beg the question, "does blockchain have the same issues?"
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
