4 ms·
I think you're overthinking this. You can just put the age-restricted portion of the website (which for some websites might be 99% of their content, but I think
by johncolanduoni 3y ago
I think you're overthinking this. You can just put the age-restricted portion of the website (which for some websites might be 99% of their content, but I think that's fine) behind a login page that verifies whatever age token you come up with. If the only information you can send to the website is your credentials, and the website can't send any "unsuitable" information to you, I'm not sure what the issue with allowing HTTP access is.
- jrockway 3y agoWell, the government has to take action against you, the site operator, if you aren't enforcing the rules correctly. That means they have to think of every possible way to monitor the traffic, both in-band and out-of-band. They then have to do this for every site on the Internet. (Or sure, just selectively enforce it against whoever X says is a threat to their ad revenue today.) When you make something, you only have to figure out one way to make it work. When you try to secure something, you have to figure out every possible way the defenses could fail, or you've done nothing.