Hacker News Reader

I left Posterous over a year before the acquisition due to a difference in opinion over strategy. Brett had also left before. I didn't agree with where my cofounder wanted to go with it. I was bummed to see it didn't work out as we had hoped when it was acq-hired. I use Posterous a ton, and I needed a replacement anyway. Thus, Posthaven. I've been working at YC since 2011, actually.

View on HN

Last year, I started using Posterous, both as blogger and developer.

As a blogger it worked fine.

As a developer it was terribly supported. The API was fine, but the implementations were often terribly flawed. Tags could not be deleted. Posts entered with markup could not be retrieved as markup. It was almost impossible to connect to an engineer at Posterous who cared.

I do hope Posthaven succeeds. I encourage you to have an API. I encourage you to treat your external developers with the respect Posterous was unable to show.

Makes sense. We've been careful to stick to RESTful endpoints so it should be a matter of creating API keys and documenting it properly.

The Posterous API was very RESTful and was my first real exploration into that. I wrote an emacs posterous blogging extension, and it was a very valuable learning experience in REST.

Reply on news.ycombinator.com