▲ 46 ▼ On the unfortunate need for an "age verification" API for legal compliance reasons in some U.S. states (lists.ubuntu.com) submitted 8 months ago by cm0002@lemmings.world to c/linux@programming.dev 13 comments fedilink hide all child comments
[+] msokiovt@lemmy.today 10 points 8 months ago (5 children) [deleted] permalink fedilink source hideshow 5 child comments replies: [–] davidgro@lemmy.world 8 points 8 months ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] lambalicious@lemmy.sdf.org 2 points 8 months ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] davidgro@lemmy.world 1 point 8 months ago (2 children) As an option, so it can automatically increment the brackets. permalink fedilink source parent hideshow 2 child comments replies: [–] lambalicious@lemmy.sdf.org 2 points 8 months ago (1 child) Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change. permalink fedilink source parent hideshow 1 child comment replies: [–] davidgro@lemmy.world 1 point 8 months ago 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. permalink fedilink source parent
[–] davidgro@lemmy.world 8 points 8 months ago (4 children) 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. permalink fedilink source parent hideshow 4 child comments replies: [–] lambalicious@lemmy.sdf.org 2 points 8 months ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] davidgro@lemmy.world 1 point 8 months ago (2 children) As an option, so it can automatically increment the brackets. permalink fedilink source parent hideshow 2 child comments replies: [–] lambalicious@lemmy.sdf.org 2 points 8 months ago (1 child) Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change. permalink fedilink source parent hideshow 1 child comment replies: [–] davidgro@lemmy.world 1 point 8 months ago 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. permalink fedilink source parent
[–] lambalicious@lemmy.sdf.org 2 points 8 months ago (3 children) 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. permalink fedilink source parent hideshow 3 child comments replies: [–] davidgro@lemmy.world 1 point 8 months ago (2 children) As an option, so it can automatically increment the brackets. permalink fedilink source parent hideshow 2 child comments replies: [–] lambalicious@lemmy.sdf.org 2 points 8 months ago (1 child) Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change. permalink fedilink source parent hideshow 1 child comment replies: [–] davidgro@lemmy.world 1 point 8 months ago 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. permalink fedilink source parent
[–] davidgro@lemmy.world 1 point 8 months ago (2 children) As an option, so it can automatically increment the brackets. permalink fedilink source parent hideshow 2 child comments replies: [–] lambalicious@lemmy.sdf.org 2 points 8 months ago (1 child) Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change. permalink fedilink source parent hideshow 1 child comment replies: [–] davidgro@lemmy.world 1 point 8 months ago 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. permalink fedilink source parent
[–] lambalicious@lemmy.sdf.org 2 points 8 months ago (1 child) Which gives away the whole birthday because applications requesting the age bracket can memorize values and notice what day they change. permalink fedilink source parent hideshow 1 child comment replies: [–] davidgro@lemmy.world 1 point 8 months ago 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. permalink fedilink source parent
[–] davidgro@lemmy.world 1 point 8 months ago 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. permalink fedilink source parent