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 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.
ohhhh but wait till you hear my stories about spinning rust... 
given your usual flash eraseblock is 4KB (or more) this is entirely possible - a drive with PLDP or an SLC cache might be able to avoid this, and an Optane drive would be totally fine with it, though - maybe that SSD has unusually large eraseblocks and very low endurance/overprov
you might be able to send a secure erase command to it and have it reappear with a few GB less capacity to confirm?
Could be - this one got RMAed, but I might try to trigger the same failure mode on the replacement and see what happens.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
