4 ms·
Terrible Approach -> Give all Posterous import tool users goatse Bad -> Block a whole rack space Good -> Negotiate some sort of deal with Posterous Better ->
by woodall 16y ago
Terrible Approach -> Give all Posterous import tool users goatse
Bad -> Block a whole rack space
Good -> Negotiate some sort of deal with Posterous
Better -> Let this site access the rss feed
Say I run a blog on the Rackspace Cloud, and want to use my own custom script to rip photos from my personal TwitPic account. Well, I can't because it is banned. In it's entirety.
It seems to have worked in the sense that the Posterous import tool no longer functions. It does not seem to work in the sense that they banned, albeit small, section of their user base.
- mrtron 16y agoFrom what perspective? From 99% of users' perspective: blocking rackspace has no effect on them unless they try to switch to posterous. You are one of a handful of users running something else on rackspace for personal use. Sure for 5 users this was a bad approach. From twitpic's persepective: it stopped them from losing users to posterous. Win.
- Terretta 16y agoWhat makes anyone think this stopped TwitPic from losing users to Posterous? I would imagine any user sophisticated enough to think of moving, would have some opinions about data liberation and services that try to lock them in. On the contrary, I would imagine this puts more users on notice that TwitPic is locking users' own data in. Such users will begin looking for other places to post pics to.
- shantanubala 16y agoNot to mention, people may already have local copies of stuff they post of TwitPic. Blocking Posterous just means re-uploading stuff, which is a nuisance. The only person who loses here is TwitPic. Unless you're as big as Facebook, you can't really monopolize user data.