[Bender]

I am not sure what you mean. Are you saying a daemon would recognize a video player that is streaming porn from within a video game? Who is installing this daemon?

A client checking for a header is more than sufficient to block small children from seeing porn and that is 100% more than we have today. No extra memory or CPU required important on tablets or phones handed to children. No privacy invasion by daemons or other third parties.

Kid: "Mommie they said go to pornhub.com for games but it ask for password"

Mom: "Dumb trolls are picking on you, I will deal with them."

[HPsquared]

The phone manufacturer. I don't think it would otherwise be possible without root. And it's quite a computationally heavy thing where security and privacy are important. It'd have to be secure (no sending information). That's why I suggested Apple, they have the vertical integration to do this kind of thing. In theory. Also it's a good counter to governments trying to censor the internet itself if children can be protected at the device level.

[Bender]

How about this. We implement RTA headers on the server and checks for the header on the clients, get little ones squared away and in parallel have Google and Apple start working on your local AI daemon. The header should take one code change cycle to get in place, maybe a couple weeks realistically assuming the goal posts are not on wheels.

[HPsquared]

But "we" are not in control of "the server". I agree though it's worth doing, adult content should be tagged as such. But it doesn't handle the case of non-compliance.

[Bender]

"We" are not in control of the server or phone client or tablet applications. Should the 5-eyes or 9-eyes countries pass a law to use RTA headers on servers and look for the header on user-agents that should suffice to get basic coverage for kiddos by default and parents can disable the checks if they so desire.