Messages 2.5 - Rethinking "9999" year in "birthdate" claim
Issue #764
duplicate
We currently use "9999" as the year in the "birthdate" claim to indicate that the year was not provided. Facebook and Google's other OAuth APIs use "0000" for this. I think we'll cause less developer confusion and bugs if we do the same.
Comments (3)
-
-
reporter -
assigned issue to
We will tentatively change back to 0000 to match existing practice. Vladimir's input is requested first, since he filed the original bug requesting us to use 9999.
-
assigned issue to
-
- changed status to duplicate
Duplicate of
#597. - Log in to comment
We changed from 0000 to 9999 because 0000 is a valid value, BC1.
See
#597