My current work acquired a company with a very poorly provisioned IT department. Their networks all happen to be in the low 192.168.0.0/16 so users VPNing in often end up with wonky IP conflicts. I’ve heard warnings about similar when selecting subnet ranges, so I just stick with low 192.168.0.0/16 ranges for home networks from which I might potentially VPN into a network I don’t control, and I use 172.16.0.0/12 or 10.0.0.0/8 at work as needed and as aligns with our wider topology.
I will also add that I encountered some fun challenges at a small bank I worked at where they clearly under-planned their network and carried a bunch of wonky configs as vestigial networking adaptations as they grew. They did do a cool thing where they made each branch its own /24 subnet so you could tell at a glance exactly what branch someone was connecting from, plus branches could theoretically limp along with an ISP outage, but they didn’t the extra steps of setting up edge servers so the end result was a full branch outage during an ISP outage
I feel like a browser API that just gives info to the site when request of either “is under age, is of age to create an account, is adult” might be an easy way to establish something like this too
This way the site can voluntarily check if they’re illegally collecting data on minors, if they’re showing adult content to adults, and automatically display age appropriate content of applicable
Maybe an NSFW flag as well that sites can check to automatically show/hide NSFW content, for example on work machines or shared computers, but that’s probably getting a little too finegrained
The real question is how is the age flag determined? Is it determined by the browser? The OS? Browser seems the safest bet, since Google can base it off of the Google Account, Microsoft can base it off the Microsoft account and Mozilla can shove it in the settings and potentially base it on the Mozilla account