Age verification becomes more common. Australia, France, etc. introduce such laws to ban children below 15 years from social media platforms, to protect them.
Will these laws also be relevant to fediverse/lemmy specifically?
Personally I think these laws will focus on the big platforms at first (facebook/meta, youtube, discord, instagramm), which will force younger users with technical skills onto smaller and niche sites. Over time focus on this question will increase for the fediverse.
It sounds like you are assuming that the wallet needs to re-validate each session and I don’t see why this would be needed. Each user account would just need to validate their age once then the website operator could store this in their database. If you’ve validated once you can be sure the user keeps being old enough.
I believe that it’s specified in the architectural reference framework that it has to re-validate every session, to ensure that the token hasn’t been revoked. I’d be happy to be corrected, though!
@yelling_at_cloud@programming.dev @SirHaxalot@nord.pub @asklemmy@lemmy.ml
Exactly! This, too. I forgot to mention it in the reply I just sent to SirHaxalot. And given the GDPR “Right to be forgotten”, an authorization must be revocable, so this means an authorization must be re-validated, even if this doesn’t necessarily mean having to go through the age check flow all over again.