2 ms·
I don't think tweeting that you've "lost a database" without any additional context is a very good idea. I'm going to guess that they meant the database was tem
by simonw 14y ago
I don't think tweeting that you've "lost a database" without any additional context is a very good idea. I'm going to guess that they meant the database was temporarily unavailable to their application servers, but it could easily be interpreted to mean that they had suffered massive data loss with no backups.
- guiambros 14y agoWell, maybe that's _exactly_ what they meant...
- simonw 14y agoThat's still not something I'd tell my (potentially non-technical) users in a tweet. Something like that deserves a LOT more context than 140 characters.
- bpatrianakos 14y agoDon't read into it so much. Losing a database means losing a database. It doesn't imply that there are no backups. Furthermore, how much detail can you really put in 140 characters? A detailed blog post would be nice but if Posterous is a small company with a handful of employees I'd say sending out a Tweet and getting back to work is a better option than spending that time explaining the specifics of what happened. That should come when it's fixed. By the way, anyone else getting a 503 error when connecting to posterous.com? Are they still down?
- simonw 14y agoI know that, but their users may not.