Live data from Hacker News

Twitter-Owned Posterous Loses Databases, Offline for 2 Hours Plus

thenextweb.com

21–24 of 24 posts

Re: Twitter-Owned Posterous Loses Databases, Offline for 2 Hours Plus

#21
post #2

Posterous was a great service until a couple of years ago. It was such a neat idea: combine blogging with mailing lists. It was simple and easy. Then they began to have multiple problems. Email notifications would fail to arrive from time to time. Various over-ajaxed functions, including composing a new post and various administrative pages, stopped working on one or another browser. I had to use Chrome whenever I vi…

i agree - loved posterous until they started the spaces thing from there it went downhill, have exported by posterous blog into octopress - and havent looked back if there are any other posterous people looking to jump to octopress i've setup http://p.ostero.us to make the move to markdown/hosted octopress painless cheers justin -- http://p.ostero.us

Your site's down, Justin.

    Connection to 173.245.61.33 Failed The system returned: Connection timed out

Re: Twitter-Owned Posterous Loses Databases, Offline for 2 Hours Plus

#22

Earlier quoted context omitted.

i agree - loved posterous until they started the spaces thing from there it went downhill, have exported by posterous blog into octopress - and havent looked back if there are any other posterous people looking to jump to octopress i've setup http://p.ostero.us to make the move to markdown/hosted octopress painless cheers justin -- http://p.ostero.us

Your site's down, Justin. Connection to 173.245.61.33 Failed The system returned: Connection timed out

prefect timing :( - coincided the unexpected outage of my site with the posterous outage

Re: Twitter-Owned Posterous Loses Databases, Offline for 2 Hours Plus

#23
post #10

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.

Well, maybe that's _exactly_ what they meant...

That'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.

Re: Twitter-Owned Posterous Loses Databases, Offline for 2 Hours Plus

#24
post #10

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.

Don'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.…

I know that, but their users may not.
Post reply on HN