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
Clearly a poor quality SSD implementation in that case... but I wonder if this is what actually happened, as opposed to just a random early failure dud. Perhaps SSD endurance tests should test this use case. Instead of writing over the entire drive, rewrite a single sector.
I bet we'd see wildly different results for different brands, and many deaths well before the specified total drive write endurance. Perhaps a good metric for how good the firmware/FTL algorithm is.
There are plenty of use cases that have this "rewrite one sector repeatedly" pattern - e.g. md-raid metadata includes an event count that basically increases every time the array is written to. I wonder if anyone else has seen this kind of early death and attributed it to this.
As someone in the industry, SSD firmware is universally crap. The only way it works as well as it does, is they hammer it into submission with testing and hope the hacks and workarounds they get in before shipping are ok enough.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
