If a local ‘date of birth’ field defaults to ‘18 and up’ if unset; the bracket is communicated using an open, standardized format; specification is on a trust-basis, without external verification required; and the field automatically unsets upon turning 18; I might not be that opposed to an implementation like this.
But without a requirement for legal presence within the state of Illinois, any application developers without it, cannot really be held liable for any infringements on it. Bad actors might also learn which internet users are of which age bracket, and this all might be the beginning of another very slippery slope, where requirements keep building as a result of misuse and/or ineffectiveness.
If a local ‘date of birth’ field defaults to ‘18 and up’ if unset; the bracket is communicated using an open, standardized format; specification is on a trust-basis, without external verification required; and the field automatically unsets upon turning 18; I might not be that opposed to an implementation like this.
But without a requirement for legal presence within the state of Illinois, any application developers without it, cannot really be held liable for any infringements on it. Bad actors might also learn which internet users are of which age bracket, and this all might be the beginning of another very slippery slope, where requirements keep building as a result of misuse and/or ineffectiveness.