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 cannot possibly fathom what one could use 10 Gbps of bandwidth for. last time I downloaded a lot of torrents my drive array bottomed out at around 180 Mbps, bottlenecked by random I/O. you'd need striped RAID and a beefy CPU and I/O subsystem to handle even 1 Gbps
3-4Gbps is easy with standard RAID on SATA rust with sequential I/O. Torrents are more IOPS-heavy, but at that point you'd set it up to download to an SSD/NVMe and move to HDD when complete. 461MB/s off my RAID6 at home. I always peg GigE with NFS.
I had a rather unusual workload where I was downloading dozens of TB of torrents simultaneously (and it wasn't really worth going RAID or SSD anyway because hashing the blocks became the bottleneck slightly above random I/O being so)
Fair enough. Personally, I could totally use a 1Gbps pipe since I shuttle data to/from servers often enough (backups, etc), but with a 100mbps connection my bottleneck tends to be the backbone. International peering seems to be getting worse rather than better.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
