hyperion2010
Joined 13 years ago
Joined 13 years ago
Now what would happen after that?
First oses would have to implement the above in a way that could not be bypassed, pretty much impossible if the child has access to the device.
Then you would need to require that websites honor that token or any similar token no matter how it was implemented ... https MITM etc. good luck with that.
Finally once all the implementation and enforcement hurdles are complete every website out there would immediately know that the user browsing was a child and all the trackers and ad networks on the web would immediately start targeting those users because children are marks.
Now you need even more laws and regulations to protect the children from being targeted by advertising companies, and good luck with enforcing that.
Unless you mean linux client, but that is presumably coming at some point now that the windows client is 64bit.
To extend the though there, the main question is not if, not when, but how long it will take. Do you bet on 90 years, 90 months, 90 days, 90 hours? Even if the change happens over 90 months (about 7 years) is that enough time to rebuild major shipping ports, forget resettling a substantial portion of the human population.
If this pep were implemented I suspect it would result in forcing thousands of not tens of thousands of people to spend hours modifying perfectly working code and destroying the ability to run old scientific code without modification. Extremely effective industrial sabotage if it were to be accepted.
It is hard for me to articulate how much peps like this reinforce my desire to never start another python project. Even if this pep is rejected the fact that there are people who would put in the time and effort to write and submit such a PEP tells me that they will do it again, and eventually they might succeed.
We'll I'm used to not being most people, but I'd much rather be able to produce a single identical binary for my users that works everywhere than the platform specific nonsense I have to go through right now. Having to maintain different special build processes for different platforms is a stupid waste of time.
Frankly this is how it always should have worked except for the monopolistic behavior of various platforms in the past.
The reason is because anyone running an os with a duress PIN that has done nothing wrong can be accused of using a duress PIN because the whole point of the duress PIN is that it looks like you just have a normal phone.
Running a normal apple operating system with just stock apps? Boom, you're a criminal because you obviously used a duress PIN and have something to hide! There is no way to prove you didn't use a duress PIN because the phone was "wiped."
Now unfortunately grapheneos probably leaks information so that a duress "unlock" can be differentiated from a standard unlock by some means. If not then kudos. It looks like it is done instantly by keeping everything encrypted and just zapping the keys, but it also needs to actually unlock to something instead of rebooting to prevent leaking the information that a duress pin was used. Not sure how fiesable that would be though.