Shane ████: "We're going to update age gating such that on mobile surfaces after you fail to enter a valid birthday a 2nd time during registration (i.e. you say you're under 13 twice), we block the app from registering new people for 2 hours or until you force close it."
Antigone Davis: "Got it on session. FWIW, I think it would be good to test what amount of time sounds reasonable to stakeholders. My guess is 2 hours will come across as arbitrary without data to back up that people don't come back after 2 hours to try again. I would expect 24 or 48 hours will"
Antigone Davis: "(Sorry accidentally hit send),... 24 or 48 hours will come across as the kind of block U13s will perceive as permanent (for now) but 2 hours will be seen as 'you don't take this issue seriously...' Another option might be random times but no less than two hours — at tleast then we can say we are trying to make it harder for them to figure out how to game the system."
Antigone Davis: "If asking for more than 2 hours means this never ships, we should take 2 hours. But I think it is better to have a time validated by external stakeholders or based on data. What is the impact 2 hours has on growth? Did growth agree to 2 hours because it is meaningless? Have we looked at accounts that try again after 2 hours to see what percent might be U13U13Under-13Users below the minimum age of 13 set by Meta's terms of service and by COPPA. "U13" denotes both the age cohort and the underage accounts Meta's own documents discuss detecting, removing, or building products for.Full entry ↗ v people who just hit the wrong age twice? If we want to claim this as a win with our policy stakeholders it has to seem meaningful to them. (PS - we should think of a term other than age gating or verifying for this as it isn't what product means by either, more like a speed bump than a gate)."
Meta & Children's Online Safety