Using files is fraught with peril https://danluu.com/deconstruct-files/ …pic.twitter.com/vmsNeSy9Sm
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 think the response on the ext4 mailing list (now added at the bottom) is also interesting. Not immediately destroying data on fsync error is a "niche use case", have to use direct I/O if you don't want random data corruption, etc.
This sort of reminds me of Meltdown, Spectre et al. Developers commit to asynchronously running ahead because it's such a huge performance benefit, and then discover drawbacks but nobody wants to back out from the idea of asynchronously running ahead given the "performance loss".
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.