not_IOsystemd moment đźâđš
rizzothesmallâ A user dob field make much more sense here. User age will change constantly and need to be maintained.
Nm, the actual code is a BirthDate in iso YYYY-MM-DD
renzhexiangjiaoactually, if the legislation doesnât specifically demand that they store userâs actual date of birth, if I were to design this system, I would simply ask the user a yes/no question of whether theyâre at least 18 at the time of answering the question. If they answer yes, it wonât expire because the time doesnât go backwards. I could also store the date exactly 18 years before the answer is given as a pseudo-DoB, that could be used, later on, to, for example, prove that the user is at least 21 for whatever reason. Most importantly, this would ensure that the user doesnât give any unnecessary identifying information to the system.
Ricky RigatoniIt would be hilarious if all thise drama, legislation, and lobbying just made a bill so poorly made weâre right back where we started.
I think the best system is an operating system that stores the exact date, but exposes it via an API that only returns a boolean. You trust your own local machine, but donât necessarily trust random apps or websites. And they donât need to know anything more than whether you pass a particular age gate.
nymnympseudonymAnthropic really deserves more kudos. They are the ones actually investing in AI alignment. They are the ones developing Constitutional AI. They publish their Constitution and system prompt. They wonât agree to mass surveillance or auto killbots.
And Claude will advocate for privacy and human rights to its last token, bless its carefully curated data set.