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

In addition to that, I get a 404 error when trying to manage the posts on my "space," and elements of the web-based post editor are no longer working. Once a post has been edited, it can take hours for it to show up on the blog's main feed. Finally, Posterous pages load very slowly these days. I stopped reporting bugs when I found that my reports were reaching an outsourced customer interaction company rather than an actual Posterous team member.

I wish the Posterous founders well on their future work at Twitter, but needless to say, I'm in the market for a new blog host.

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 visited my family blog because things would not render properly in Firefox. Then I had to go back to Firefox because files wouldn't upload properly in Chrome. I suspect the problems had to do with the introduction of the "Spaces" thing, which AFAIK never really took off. I didn't even bother to complain because by that time, I'd stopped Posterous for anything important anyway. Then they were acquired by Twitter, and around the same time, most of the problems I'd been experiencing mysteriously went away.

It's sad to see such a great service slowly killing itself. First they ruined a perfectly working product by slapping half-baked social-networking bullshit on it, and then they got acquired by a company that has little to do with email blogging. On the plus side, they seem to have stopped developed "Spaces" since the acquisition, which probably helped prevent the further introduction of bullshit and unstable features.

I think spaces made it sort of awkward and was disappointed that it essentially stopped development since being acquired by twitter. I'm starting to wish these acqui-hires were more focused on improving the product rather than just getting the programming team to work on completely different products.

Also, there's probably a fail-whale joke in here somewhere :-)