Posterous - Beacon of Data Portability
techtruth.tumblr.com
techtruth.tumblr.com
What hypocrisy?
We find it much more effective to have an API that other people (like you) can use to write an exporter to whatever other service they wish.
Maybe you should just write a Posterous exporter using our API, instead of complaining. Just let me know if you need any help!
thanks
When they block and threaten legal action against a company for writing a custom "importer" to pull content from Posterous - then you have hypocrisy.
Smells like astroturfing to me.
Your argument is flawed and you are changing your base premise when called out.
http://posterous.com/api/reading
What exactly are you looking for? We're open to suggestions and will gladly expand our API to keep Posterous open and flexible.
There's no hypocrisy here. Our goal is to let users move into and out of posterous at will, and use whatever service they find to be best.
Thanks!
I'm sure if I do, I'll put it up on GitHub. The biggest concern I have is not only getting the content of posts, but being able to make a .htaccess with redirects so that I don't lose my google juice.
But at the same time, I'm a programmer. I love to tinker. I'd much rather have something that runs on my own server, and lets me do whatever. There's a few widgets and things I'd like to add, or at least experiment with. I can't do that with Posterous.
Additionally, the whole affiliate link thing left a bad taste in my mouth. If I already hadn't been considering switching, it probably wouldn't have been enough, but it moved my thinking from "maybe I'll switch someday" to "I'm going to switch someday."
One of the reasons I haven't switched yet is that I don't feel there's a clear winner in the blogging space. I like Tumblr's look and feel, but that doesn't solve my portability or customizability concerns. I'm trying to fight the urge to start typing 'rails g post title:string body:text' because I really don't have the time to do all of that... I've been thinking about trying Wordpress 3, but with it's security history, I'm a little shaky. I used to use Jekyll, and enjoyed it, so that might also be where I go.
Deleted comment
If Posterous is open about data portability, customers will be happy as well.
I'm sick of all these companies talking shit but not being able to back it up when they say they're looking out for the user!
http://en.blog.wordpress.com/2010/02/09/posterous-importer/
There's information and a direct link to a plugin that lets you export your site out of Posterous to Wordpress.
We think we're a better service than they are, but we aren't afraid of data portability. Users can switch as much as they want and choose the best service
Is it really a web app company's responsibility to actually write importers for competitors? It's certainly a responsible practice to document the API well, but you're basically asking for your landlord to pay for your moving van when you move out.
If you were defending tumblr or trying to make posterous look bad, I don't think you did any good here.