Keeping kids safe online is a top priority.

Today, the Commission has preliminarily found porn platforms Pornhub, Stripchat, XNXX, and XVideos in breach of the Digital Services Act for allowing minors to access adult content.

We鈥檝e also launched investigation into Snapchat under doubts that the platform has failed to adequately protect minors from harmful content, grooming, and illegal products like drugs and vapes. We also suspect that they have failed to verify users age sufficiently.

We say this loud and clear: online platforms are responsible for protecting minors, and they need to do more to deliver on this responsibility.

The full press releases:

馃敆 https://ec.europa.eu/commission/presscorner/detail/en/ip_26_722
馃敆 https://ec.europa.eu/commission/presscorner/detail/en/ip_26_723

@HennaVirkkunen How is that to be done without handing these platforms our identities and ability to track us? Seems the last thing I want is for them to be trusted with anything.
There is a simple way: the EU establishes a 芦neutral point of identity禄 similar to the passage of Spanish administration https://pasarela.clave.gob.es/. Just the regulation enabling it have to make sure it doesn't store data on which sites you visit.

This service only has to respond to the provider's request affirmatively or negatively given legal conditions to access its site.

CC: @[email protected]
Ministerio de Asuntos Econ贸micos y Transformaci贸n Digital

@david @bjoreman @HennaVirkkunen that site somehow doesn't seem to work here. But in general, these proposals fail, because sites can regularly probe for age brackets. If you do this on a regular basis, you can figure out someone's birthday.

E.g. if 12 years is a bracket boundary, the day that age gets attested is the birthday of the kid. Even more likely because someone is more likely to check close after their birthday to unlock some site/functionality.

Excuse me Dani毛l, but I don't understand the problem. Wasn't the goal to prevent people under the legal age from accessing the service? Once that was achieved, what's the failure?

CC: @[email protected] @[email protected]

@david @bjoreman @HennaVirkkunen The problem with most age attestations is that you can work out someone's birthday by keeping track of past attestations. When the attestation changes, someone had their birthday, thus the attestation gives away information that someone might not want to reveal.

This gets worse with implementations with which you can test age brackets (different age brackets under 18, to allow some content).

@david @bjoreman @HennaVirkkunen So, the problem with age verification is that it is yet another attack on privacy. Not surprisingly, behind the scenes Meta is pushing this a lot through various sock puppets.

@david @bjoreman @HennaVirkkunen Also, age verification is strongly detrimental to open source and your freedom to choose your OS.

Most implementations of 'anonymous' age verification require remote hardware attestation (eventually), because otherwise you can manipulate the app/process that partakes in the attestation.

Mandatory remote attestation is pretty much the end of free OS choice, because you running your own non-approved software will shut you out of services.

@david @bjoreman @HennaVirkkunen Age verification + remote attestation is big tech's pipe dream. Google can already shut out competing systems from phone NFC payments, because pretty much every bank only supports Google/Apple Pay and Google doesn't attest alt-OSes.

Remote attestation of websites would be another level, making it practically impossible to live outside the Google/Apple duopoly.

Do not add Google Play Integrity integration 路 Issue #18 路 eu-digital-identity-wallet/av-doc-technical-specification

In the README, the following is listed: App and device verification based on Google Play Integrity API and Apple App Attestation I would like to strongly urge to abandon this plan. Requiring a depe...

GitHub