3 ms·
I don't know. I haven't touched that feature in a while. But there's a philosophy that you own your content, but connections are owned by both ends. I'm not eve
by orijing 15y ago
I don't know. I haven't touched that feature in a while. But there's a philosophy that you own your content, but connections are owned by both ends. I'm not even sure that being able to export your wall (including others' private comments) is fair to others. Otherwise, you end up with Google's public-sharing bug (where you can share a private item publicly).
There's a fine balance between respecting your privacy and flexibility, and those of your friends.
- rxin 15y agoThis argument is too weak to sell. In the same realm, you should remove from the zip file photos that contains the user's friend(s).
- jeffdavis 15y ago"Otherwise, you end up with Google's public-sharing bug (where you can share a private item publicly)." If you share something digital with someone, they can share it with someone else. That's just the way it is. Interfaces and clients should help you avoid doing that accidentally, and even make it slightly challenging (perhaps you need to write a new client against their API or something) -- but preventing you from exporting your own data, or data that someone has explicitly shared with you, is just not justified. It sounds a lot more like a convenient excuse for lock-in.