If we want to protect kids/teens, why not create an "Internet for kids" with a specific TLD, and the owner of this TLD would only accept sites that adhere to specific guidelines (moderation, no adult content, advertisement...)? Then devices could have a one-button config that restricts it to that TLD.

▲

vmg12 3 days ago | parent | next [-]

I'm not suggesting solutions to any of these things, I'm also not one of the "think of the kids" people.

▲

dizlexic 3 days ago | parent | prev [-]

Why have I never heard this idea, you're a genius. Can we ship this next week?

This current approach is a net negative, but the TLD idea actually makes sense to me.

▲

thfuran 3 days ago | parent [-]

And as long as kids don't know about DNS, it might even work.

	▲	astrobe_ 12 hours ago \| parent \| next [-]
		Well, in this scenario the user isn't supposed to have access to the (DNS) configuration. But one could still enter a raw IP address in the browser - e.g. a friend who has an unlocked device could ping the site to get it. But if one accesses a website by IP, since the links and the Ajax often need DNS resolution (CDNs etc.), the content will probably be blocked for the most part. Like copy protection, the scheme is probably not entirely waterproof, but it can nonetheless act as a deterrent.
	▲	dizlexic 3 days ago \| parent \| prev [-]
		Meh can be implemented at many different levels.