Hacker News new | past | comments | ask | show | jobs | submit login

They absolutely get a say - they can choose to put it on posterous, or not. They can also choose to put their data wherever they want.

What they don't get to do is force a business, unless it's part of a paid-for contract, to spend it's own resources and bandwidth to help an unrelated competitor (or anyone else).




It's own resources and bandwidth being a public facing RSS feed. A public data feed! If they don't want people to use their data feeds to, oh, I don't know, get data, then maybe something else is up. They are digging deep to find excuses rather than digging deep to compete. It's like if your girlfriend wants to break up and move away and asks for a ride to the bus station. Don't tell her to walk, show some class and help her go.


If a user wants to move from TwitPic to Posterous and TwitPic decides to block the simplest method of doing so, they are clearly in the wrong. Do you really think Posterous-generated traffic is significant compared to their usual traffic?


That wasn't really the point I was making - do I think it's a traffic problem? Probably not.

My point was that it's not about user's "rights" about their data - none of those are really being taken away - I don't like the sense of entitlement everyone wants - it's just going to breed gigantic TOS documents and legal hassles. Twitpic may very well be making a very bad PR move here (rather than spending the money innovating and competing)


Ok, I see what you're saying. I think the expectation that users will be able to get their data back out of a service if they choose to do so is a good one, and that services that don't meet that expectation should be criticized and avoided.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: