|
|
|
|
|
|
by hankbond
23 hours ago
|
|
|
I feel like this blends two discrete things 1. Can I have access to my data (the side effects of my interaction with an application) in a portable way? 2. Can I stop or prevent others (like the application author) from having access to my data? I wonder which -- if users had to choose -- they care more about? I think for most uses its #1 unless its very personal data, in which its #2. I love the idea as presented in this article but I'm not so sure how practical it is. I don't know how much overlap there is between "author has to run application a central server" (can't just be a local app) and "author must not retain data". Seems like a really awkward space to inhabit. |
|
|
Hello there! I agree users may want one or both of these features in their interaction with an application, and that their preferences likely vary depending on the type of data we're considering. The way I'm reading what you're saying, there's some sort of tension or tradeoff between the two features that I don't fully understand. Can you help me understand it a bit better? Thank you!