You request a one-time-certificate with a smartphone, then copy it on a laptop (already this is not automatic): once per website or page? That is a lot of certification requests. And that would be to access the content in the www? It creates a dependency stronger than DNS. And there should be full warranty that the issuer and the receiver cannot cross information (of the issued and the received - that would identify the user).
Plus, not everybody has a smartphone. Not everyone accepts Android or iOS at their current implementations. Do those people remain without access to the www?
Last week I logged into my e-gov website by confirming a push notification on my authenticator app that's tied to my e-ID card to download my birth certificate. No copy pasting needed. Random websites now even support logging in without passwords by using your smartphone passkeys.
I am sure they can make it work for a simple yes/no (over 18) challenge-request scenario.
> Plus, not everybody has a smartphone. Not everyone accepts Android or iOS at their current implementations. Do those people remain without access to the www?
We are talking about adult content. The alternative is having that content banned. Many democratic countries have already done that, like South Korea. I don't prefer this scenario.
I don't necessarily agree we need this, but to claim it's impossible to do this in a secure way is ridiculous.