What hypocrisy?
Posterous - Beacon of Data Portability
11–20 of 30 posts
Re: Posterous - Beacon of Data Portability
#12If Posterous wants to be a STAND UP company, they'll post information and a tool(not just XML or API) on how to migrate away FROM Posterous. Then they can go and write importers for other sites. 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!
Re: Posterous - Beacon of Data Portability
#13When they block and threaten legal action against a company for writing a custom "importer" to pull content from Posterous - then you have hypocrisy.
Re: Posterous - Beacon of Data Portability
#14For the record: Posterous API allows 100% access to your data on Posterous. Users own their content and are free to move. -Sachin Agarwal ( http://bit.ly/9MYzfP ) What hypocrisy?
Re: Posterous - Beacon of Data Portability
#15As far as I'm aware, Posterous has done nothing to actively discourage migration of information away from their service, and they certainly haven't threatened legal action on anyone for moving their online information around.
I am simply asking Posterous to take moral high ground. Give a feature where people can export their posts in standard data formats. then go ahead and target your competitors.
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!
Re: Posterous - Beacon of Data Portability
#16For the record: Posterous API allows 100% access to your data on Posterous. Users own their content and are free to move. -Sachin Agarwal ( http://bit.ly/9MYzfP ) What hypocrisy?
Can normal users know how to use this API? Why don't you give a button which says export my posts to a text file or something else.
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
Re: Posterous - Beacon of Data Portability
#17For the record: Posterous API allows 100% access to your data on Posterous. Users own their content and are free to move. -Sachin Agarwal ( http://bit.ly/9MYzfP ) What hypocrisy?
Can normal users know how to use this API? Why don't you give a button which says export my posts to a text file or something else.
Re: Posterous - Beacon of Data Portability
#18If Posterous wants to be a STAND UP company, they'll post information and a tool(not just XML or API) on how to migrate away FROM Posterous. Then they can go and write importers for other sites. 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
Re: Posterous - Beacon of Data Portability
#19Earlier quoted context omitted.
Can normal users know how to use this API? Why don't you give a button which says export my posts to a text file or something else.
Because what are you going to import that file into? Everything needs a custom import format. Making the API available makes it easy for someone to write something that exports to the format needed. Do you think Posterous should host a different file that allows easy importing for all of its competitors? If the competitors care, they can make a tool that imports into the format they desire. Likewise, if a user just w…
Re: Posterous - Beacon of Data Portability
#20I was actually considering making such a tool, because I'm pretty sure that I'm moving away from Posterous in the near future. 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.