This new "privacy" law will require that all operating system providers must start collecting your birth date every app you install will need to ask your OS provider for that information. It's whac...
The comment you answered to said not all software has to implement age checks; only those who actually deal with age relevant content. You said it would be a foot in the door. So… who’s foot to do what?
i mean in the sense this sets up the infrastructure for and normalizes invasive identification systems that could in the future be used to say, demand your id or face scanning for you to even access the internet or use computers at all, not just age restricted stuff. of course we can only speculate how they could use this for nefarious purposes.
as in a slippery slope, might have been a better way to put it.
Its not invasive yet (no third party, no ID, no verification; its basically just another user controlled date field that is not even exposed). So it is not lowering any barrier in that regard.
It’s also not a helpful intermediary step for harder measures, because as soon as you want a third party to do attestation, storing that on a user controlled device is just unnecessary complexity and risk of circumvention. It would be easier and safer (for those introducing it) to just let the attesting party talk to the providers directly.
i don’t get your question. what do software like krita has to do with anything?
The comment you answered to said not all software has to implement age checks; only those who actually deal with age relevant content. You said it would be a foot in the door. So… who’s foot to do what?
i mean in the sense this sets up the infrastructure for and normalizes invasive identification systems that could in the future be used to say, demand your id or face scanning for you to even access the internet or use computers at all, not just age restricted stuff. of course we can only speculate how they could use this for nefarious purposes.
as in a slippery slope, might have been a better way to put it.
How would the current approach help?
Its not invasive yet (no third party, no ID, no verification; its basically just another user controlled date field that is not even exposed). So it is not lowering any barrier in that regard.
It’s also not a helpful intermediary step for harder measures, because as soon as you want a third party to do attestation, storing that on a user controlled device is just unnecessary complexity and risk of circumvention. It would be easier and safer (for those introducing it) to just let the attesting party talk to the providers directly.