On Jan 24, 2009, at 5:17 PM, Tango the Mutt wrote:

> (Take 2, as I replied to Denise first on accident.)
>
> Denise Paolucci wrote:
> *SNIP*
>
>> (Yes, we know that there's cases where someone might legitimately
> want to *display* a birthdate that has them under 13, while they
> themselves are over 13. This is why we'll make it very clear that the
> signup birthdate should be YOUR ACTUAL BIRTHDATE, and you can set the
> displayed birthdate later.)
>>
>
> Are these going to be treated as separate fields? I can see reasons to
> make them separate and reasons to keep them together. What is the plan
> for Dreamwidth?

LJ separated the two (signup DOB and profile DOB) sometime in '06,  
IIRC. I've yet to investigate if those changes are livejournal or  
ljcom, but if they are ljcom, we need to replicate them into  
Dreamwidth; it gives you problems under COPPA to allow people to  
change their signup DOB after signup. (And it looks bad to third  
parties, ie the FCC, that would be bringing action under COPPA.)

For instance, say I'm writing journals for my two cats, age 12 and 5.  
I sign up, I put in my DOB because that's what the site says to do,  
then I put the cat's DOBs in the journals' profiles. If we do *not*  
store the DOB given at account creation, and the FCC comes along and  
sees that omg there's a five-year-old on this service, that can count  
against DW as a COPPA violation (with associated heavy fines). If we  
store the DOB given at account creation, we can turn around and say  
"no it isn't; here's the DOB given at account creation, which clearly  
indicates that the person is over 13".

That saves us the hassle of having to go through journals that are  
reported for being under 13 and trying to determine if they're  
fictional or really belong to a 13-year-old. If the DOB given at  
signup is over 13, they're over 13, period.

(Yes, people can lie on signup. But that's not DW's problem.)

--D



-- 
Denise Paolucci
[email protected]
Dreamwidth Studios: Open Source, open expression, open operations.  
Coming soon!

_______________________________________________
dw-discuss mailing list
[email protected]
http://lists.dwscoalition.org/cgi-bin/mailman/listinfo/dw-discuss

Reply via email to