This is the wrong approach to keep kids off porn sites. Web platforms at most should just be adding an RTA header to anything that contains porn or user-generated content. That's it, nothing more for platforms. Headers missing? State(s) warn the company, then the state(s) fine the company.
The popular web clients must then recognize that header and check if parental controls are enabled. If so, then the client must check if the domain has been approved by the device owner. That's it, nothing more for clients. Liability is on the parents and off the platforms. No uploaded faces, SSN's, addresses, state ID's, and other PII that will ultimately be leaked, stolen, sold, etc...
This intrusive and irresponsible method of validating people will just push most small platforms underground i2p, tor .onion sites, encrypted Usenet, open source vpn mesh-nets eventually authenticating with something like ActivityPub to share public keys, etc and push most people to use VPNs to access the bigger platforms.
The popular web clients must then recognize that header and check if parental controls are enabled. If so, then the client must check if the domain has been approved by the device owner. That's it, nothing more for clients. Liability is on the parents and off the platforms. No uploaded faces, SSN's, addresses, state ID's, and other PII that will ultimately be leaked, stolen, sold, etc...
This intrusive and irresponsible method of validating people will just push most small platforms underground i2p, tor .onion sites, encrypted Usenet, open source vpn mesh-nets eventually authenticating with something like ActivityPub to share public keys, etc and push most people to use VPNs to access the bigger platforms.