An alternative one could consider is that the ISP could DNS-block sites for "kid SIMs"). On the OS part, this would require protection against picking alternative DNS, but that's already standard. Other "anti-circumvention" features might be required, such as factory reset.

For all the protections that the ISP cannot reasonably provide, one can consider creating a nation-wide (or EU-wide, or US-wide) official label, that device makers can obtain if they meet certain requirements. Parents can them make their choice. We have that for food etc., so why not for internet access mobile devices. Because from my perspective, the main problem that needs to be solved is that parents cannot monitor 24/7 what their children do on their phones.

Yet another solution is to create a top level domain for kids, restrict kid devices to that domain, and allow sites enter this domain only if they meet defined criteria.

Oh, and prevent ISPs and phone makers to sell 'for kids" products at a higher price. People can whine all they want about free market, but it's to protect our children.

▲

walrus01 5 hours ago | parent [-]

Whenever I see people say "oh we should just get the ISPs to block it!" I wonder if they work at any ISP, or are just an end-user consumer of their services... As someone who does work in the ISP/telecom infrastructure sector my first reaction is hell no. I do not want US/Canadian ISPs to go down the path of what has happened with, for instance, Spanish ISPs DNS-blocking football related things as a result of court orders.

	▲	astrobe_ 3 hours ago \| parent [-]
		I am not, indeed. However as programmer I was sometimes told to do what the customer wants, even though it is complex or inapt. If this DNS blocking is inapt or misused, it's a political problem so let the citizens deal with it (I know this seems like wishful thinking given the current poor state of politics at least in the EU, but hopefully we will fix that while it's still in our hands). Besides, I read about what happened with Spain and football, and from my understanding the issue was that they blocked not DNS but IP addresses. And problem domain is also vastly different, a priori: in that case, they faced sites that were actively trying to avoid blocking, while in our case, I doubt pron sites and such will try to do the same, because children are not their target audience. An alternative could be to create a top level domain (TLD) "for kids" and restrict kid phones to it. Then in your TLD you can admit sites that meet minimum criteria (no pron, no terrorism, content and chat moderation for SNS).