cm0002@lemmings.world to Linux@programming.dev · 2 days agoOn the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. stateslists.ubuntu.comexternal-linkmessage-square13fedilinkarrow-up150cross-posted to: linux@lemmy.ml
arrow-up150external-linkOn the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. stateslists.ubuntu.comcm0002@lemmings.world to Linux@programming.dev · 2 days agomessage-square13fedilinkcross-posted to: linux@lemmy.ml
minus-squareMugita Sokio@lemmy.todaylinkfedilinkEnglisharrow-up10·2 days agoCanonical can kiss my behind if they want to implement digital ID.
minus-squaredavidgro@lemmy.worldlinkfedilinkarrow-up7·2 days agoIt’s not though. It’s literally asking the user “how old are you?” and not even caring if they lie. It’s not even requiring a date, just a number of years.
minus-squarelambalicious@lemmy.sdf.orglinkfedilinkEnglisharrow-up2·1 day ago It’s not even requiring a date, just a number of years. Several posts in the mailing list thread specifically mention adding Y, M, D fields for DOB.
minus-squaredavidgro@lemmy.worldlinkfedilinkarrow-up1·1 day agoAs an option, so it can automatically increment the brackets.
minus-squarelambalicious@lemmy.sdf.orglinkfedilinkEnglisharrow-up2·1 day agoWhich gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change.
minus-squaredavidgro@lemmy.worldlinkfedilinkarrow-up1·21 hours agoThat is a good point. Websites also if they are visited daily or if a web beacon or such can access the API. Manually adjusting the brackets until 18+ (or just lying about the precise date) would grant more privacy. I can see making that trade-off though.
Canonical can kiss my behind if they want to implement digital ID.
It’s not though. It’s literally asking the user “how old are you?” and not even caring if they lie. It’s not even requiring a date, just a number of years.
Several posts in the mailing list thread specifically mention adding Y, M, D fields for DOB.
As an option, so it can automatically increment the brackets.
Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change.
That is a good point. Websites also if they are visited daily or if a web beacon or such can access the API.
Manually adjusting the brackets until 18+ (or just lying about the precise date) would grant more privacy. I can see making that trade-off though.