Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Speaking as a Brit, I wish Wikipedia would just go black for the UK. That might focus some minds.

Likewise. People (organisations/companies), as far as possible, shouldn't be pandering to this stuff, it's not the answer, it doesn't help them or us.



What is the answer?


To online safety for children? The same as offline safety; parenting and education. There's not much money in those though.

https://x.com/moo9000/status/1950866445186818209


Making content restrictions easier for parents to implement would help a ton — like being able to block all sites in a browser and create a whitelist of the ones kids are allowed to access. Similar whitelisting should be available and easy to implement for YouTube and social media. Having to individually block each site/video/profile you don’t want your kid to access is a futile game of whack a mole.


A more sensible approach to this law would be to require adult sites to include a clear marker in either an HTTP header or an HTML meta tag. For example:

<meta name="OnlineSafetyAct:SiteClassification" content="adult;nudity">

This would allow locally run browser content blockers to automatically detect such sites without blocking them individually, and it would be trivial for site operators to implement. Since it would be mandated by law, sites that refuse to comply could be subject to legal action.

Of course, this would still rely on parents taking the basic step of setting up a content blocker before allowing their children unrestricted internet access.


You can do something like this currently with schema.org metadata:

    {
      "@context": "https://schema.org",
      "@type": "WebPage",
      "contentRating": "18+",
      "isFamilyFriendly": false,
      "audience": {
        "@type": "PeopleAudience",
        "suggestedMinAge": 18,
        "requiredMinAge": 18
      },
    }
- https://schema.org/WebPage

- https://schema.org/PeopleAudience

- https://schema.org/AdultOrientedEnumeration


But you can do this now: I made this for my sisters kids and my friend his Alzheimer dad years ago. Agree: its not mainstream or installable by just anyone, but if you are on HN it will take an old laptop with linux and chromium and a few hours.


I'm able to do this using the Google Family controls for my kids' mobiles. I've tied it down so much that they use them rarely and for specific purposes.


This is already fairly trivial to do. There are many DIY and commercial off-the-shelf solutions. The problem with all client-side blocking is that it can be bypassed by just...using a different computer. People who want this legislation want restrictions to apply everywhere, not just on parent-managed devices, so shifting the discussion to client-side blocks just makes our arguments trivial to dismiss as irrelevant.


I wish it was as simple as that


Definitely not current legislation at least, which is making things worse for everyone.


>What is the answer?

WHITELISTING. It's utterly infuriating the obvious, time tested strategy with all the technological pieces already in place and an easy slot-in for government isn't at the tip of everyone's tongue. Just setup a set of new TLDs, ".kids1", ".kids2", ".kids3" etc, with kids1 being appropriate for anyone ages 0-4 years old, kids2 ages 5-9, kids3 ages 10-14, etc. Or whatever permutation experts and the public say make the most sense. Governments can set the requirements for anyone or any organization who wants to register a domain there to ensure all content is controlled, no user submitted content (or only submissions from registered people/orgs like schools say), no algorithmic engagement usage allowed, no advertising or whatever else is desired. It's also trivial to add that in under country TLDs so every single nation that wants to regulate their own can do so to their own standards. An alternate similar approach would be to have a single ".[ccTLD].kids" domain and then legally required DNS txt info site-wide as well as standardized metadata tags at the top of every single page going into more granular detail about content by category (like if some parents though their kids were ready for a higher age bracket of world news before being ready for a higher bracket of something else).

With age-appropriate content under its own TLDs, all the other technical pieces are easy to slot in as well. It'd be absolutely trivial for OS makers to have parental control mode simply gate a given user into whatever TLDs match the age or content levels set by the parents. It's very easy to imagine a nice GUI at the router level combining TLD-restrictions with VLANs and PPSKs such that a parent can "add a child" and it spits out a separate WiFi password that gates the child into their own age appropriate stuff.

The general internet should be a free for all for adults (or adult level), period. Access at all should imply someone is ready to navigate it. Trying to restrict and sanitize it is evil, wrong, and also just plain fucking stupid since it'll never work well. We can easily make a child internet however.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: