| ▲ | walrus01 6 hours ago |
| Building this functionality into an operating system is an extremely slippery slope to even further centralized corporate and government authoritarian control of people doing what they want with the personal computing devices that they own and possess. |
|
| ▲ | scronkfinkle 6 hours ago | parent | next [-] |
| I think you may be misunderstanding a bit. There's no forced verification. It'd be more of an RFC that gives parents the ability to communicate their underage child is using the device without revealing or verifying any further information. Or do you suspect that giving any ground will cause the ID verification and centralized behavior? |
| |
| ▲ | hgoel 6 hours ago | parent | next [-] | | I think the concern is a forced bit of functionality in all operating systems. It would quickly lead to a "and you need a license to sell your device so we can check that it can't bypass mandatory chuld-safety guards". Just like how some politicians are proposing mandatory licensing for releasing any AI model. | | |
| ▲ | LadyCailin 5 hours ago | parent [-] | | You need licenses for a lot of things though, particularly for things where there is substantial harm to be done when done incorrectly. This is just how it goes as things get more popular. Think back to 1903, there was no FAA then, but also no need for one. But it would be super disingenuous to argue now that airspace should be totally unregulated. I think the problem with this debate in general is that people aren’t recognizing the harm, and are clinging on to old ideas about how the world should work, ideas that just don’t acknowledge the reality of how things change as technology changes, or even just spreads. Rejecting the idea that there are harms, and thus nothing should be done, just ensures you don’t have a seat at the table at all when it comes to the inevitable decision to do the regulation. | | |
| ▲ | lukeschlather an hour ago | parent | next [-] | | I think you aren't recognizing the harm of collecting this information. I might be okay with this if companies were banned from using age for targeted advertising. However, the other harm is the recent IDScan hack which leaked 153M people's IDs. And regulation is not a solution here, we don't know how to implement a regulatory regime that will prevent these sorts of privacy disasters. Even if IDScan gets fines which kill the company (and I suspect they will not) it's not enough of a deterrent because no one will pay enough to actually provide proper security here. | |
| ▲ | hgoel 5 hours ago | parent | prev [-] | | Licensing for selling anything with a computer in it would cripple competition from small incumbents. They're mostly just regulatory capture for the established players that created the problem in the first place. Age restrictions are also an implicit statement that they are allowed to continue doing the same harmful things to adults. Meta, Google, Anthropic, OpenAI etc can afford to pay for and deal with licensing. They also created these issues and would very much prefer not to have to mitigate the harm they do to adults (i.e. people with money to spend). Furthermore, it'd be great if they didn't have to worry about small time competitors emerging and growing too fast. Licensing under the guise of "think of the children" is perfect for them. |
|
| |
| ▲ | 1dom 5 hours ago | parent | prev | next [-] | | I think you need to explain the solution you're thinking of in detail. "an RFC that gives parents the ability to communicate their underage child is using the device without revealing or verifying any further information." is no different to "turn on age lock?" that you see on website now. It requires the parent to be present, engaged and 1 step ahead of their kids, and if we could depend on that, then we wouldn't even be having this discussion. | | |
| ▲ | asadotzler 2 hours ago | parent [-] | | He was saying, vendors put that flag in the OS and parents set that flag in the OS and internet services respect that flag from the OS. No website anything, all in the OS. No staying ahead of anything, one and done. This, as noted above, requires that services respect the flag, which they do not universally do today. That requires legislation, something that will be a part of any workable solution. |
| |
| ▲ | walrus01 6 hours ago | parent | prev [-] | | I suspect that communicating a flag value of boolean true/false that "this computer is in use by a minor" from the operating system (via browser or app) to a remote SaaS service like something run by Anthropic will be seen as insufficient by the SaaS, so they'll necessitate ID-scan/live-selfie verification anyways. Meanwhile, the age flag in the operating system will be used for other forms of authoritarian control. It will have actually accomplished nothing other than limiting peoples' fundamental civil liberties. | | |
| ▲ | scronkfinkle 6 hours ago | parent [-] | | That's a valid take. The issue I'm wrestling with is the inevitable attempts to point a finger at who is responsible when bad things happen. If you claim it is on the tech companies to know if a child is online, then they will take the safest path for them by forcing ID verification in independent adhoc manners. This is what we are seeing now, and to me this is the worst situation. If you shift the responsibility more to the parents (this child was using a device that didn't send the `PARENT_CONTROL` flag, therefore we assumed they were an adult) it's a completely different conversation. Furthermore, if something happens to a child AND it's obvious from traffic logs that the platform willingly knew a child was being talked to, then that is also a completely different situation than the first. Leaving it all completely deregulated and/or letting platforms implement it themselves to varying levels of success and personal invasion feels like the worst option to me. |
|
|
|
| ▲ | astrobe_ 5 hours ago | parent | prev [-] |
| 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). |
|
|