undefined | Better HN

0 pointswhynotmaybe26d ago0 comments

How does that apply to windows server with active directory for a school ?

Does that mean that the admin will have to manage dob of every student when creating accounts ?

> A developer shall not willfully disregard internal clear and convincing information otherwise available to the developer that indicates that a user’s age is different than the age bracket data indicated by a signal provided by an operating system provider or a covered application store.

>If a developer has internal clear and convincing information that a user’s age is different than the age indicated by a signal received pursuant to this title, the developer shall use that information as the primary indicator of the user’s age.

So, I have a button "I'm older than 18" on my app but the signal is "under 13", I can decide that the user is older than 18 ?

0 comments

cptroot26d ago

So because there is no requirement for the age to be accurate, it would be pretty easy to say "all student accounts are the age of the youngest allowed school entrant for that school year", right? That resolves the age issue and also prevents both PII leakage as well as possible school bullying opportunities.

jkrejcha26d ago

> Does that mean that the admin will have to manage dob of every student when creating accounts ?

That already happens to some extent although the mechanism by which this happens might depend on the school district, etc. The `dateOfBirth` LDAP attribute is probably the most obvious method (which admittedly should probably not be used due to the ease in accessing this info in the default configuration) but there are others.

In secondary school when my account was set up we were told that our initial password (that we had to change on first logon) was our DOB

j / k navigate · click thread line to collapse