4 ms·
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,
by jerrya 14y ago
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.
- garry 14y agoMakes sense. We've been careful to stick to RESTful endpoints so it should be a matter of creating API keys and documenting it properly.
- jerrya 14y agoThe 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.