3 ms·
The boundary should be that user generated personal data that is on a user device should stay personal on a user device unless explicit consent is otherwise giv
by throwrqX 5y ago
The boundary should be that user generated personal data that is on a user device should stay personal on a user device unless explicit consent is otherwise given. That's it. The argument is always well "don't you want to save the children" to which I give this example.
In the USA guns are pretty freely available, relative to other countries. There is a huge amount of gun violence (including shooting at schools targeting children) yet every time major gun restriction legislation is introduced it fails, with one major reason being the 2nd amendment of the US constitution. This could again be amended, but sufficient support is not there for this to occur.
What does this say about the US?
They have determined, as a society, that the value of their rights is worth more than all the deaths, injuries and pains caused by gun violence. A similar argument can be made regarding surveillance and child porn, or really any other type of criminal activity.
- thesuperbigfrog 5y ago>> The boundary should be what is on a user device should stay personal on a user device. But how many apps only store the locally on the device versus sending data to the cloud, getting data from the cloud, or calling cloud APIs to get functionality that cannot be provided on device? Having the power of a personal computing device is huge, but having a networked personal computing device is far greater. Keeping everything on-device is a good ideal for privacy, but not very practical for networked computing.
- throwrqX 5y agoAh, I was talking specifically about user generated personal information. I have edited my post to make it clearer.