LJ flags another comm as 'Explicit Adult Content'
Thursday, July 8th, 2010 02:25 pmLJ forces a comm to declare itself Explicit Adult Content, then after complaints from the comm owners, changes it to Adult Concepts.
http://ineptshieldmaid.dreamwidth.org/192601.html
While I don't really approve of LJ's policy, although I do acknowledge they are within their rights to have such a policy, I'm confused as to why anyone is surprised by this. This has been LJ's stated policy for a long time (possibly ever since the flag was introduced?), and just a while ago, the exact same thing happened to fanficrants.
And, although people are referencing the ToS, the FAQs clearly state that this is the policy:
http://www.livejournal.com/support/faqbrowse.bml?faqid=281
http://www.livejournal.com/support/faqbrowse.bml?faqid=196
http://ineptshieldmaid.dreamwidth.org/192601.html
While I don't really approve of LJ's policy, although I do acknowledge they are within their rights to have such a policy, I'm confused as to why anyone is surprised by this. This has been LJ's stated policy for a long time (possibly ever since the flag was introduced?), and just a while ago, the exact same thing happened to fanficrants.
And, although people are referencing the ToS, the FAQs clearly state that this is the policy:
http://www.livejournal.com/support/faqbrowse.bml?faqid=281
http://www.livejournal.com/support/faqbrowse.bml?faqid=196
no subject
Date: 2010-07-27 09:32 am (UTC)no subject
Date: 2010-07-27 12:30 pm (UTC)In this case, the policy dates back to when the feature was introduced, as far as I know, and while I am not 100% positive, I have the inkling that it was in fact mentioned when the feature was rolled out, and ... this is not quite on the same level as "surprised water is wet; surprised fire is hot", and I had not thought that it was obscure enough to be "surprised that the user-head links to the profile".
no subject
Date: 2010-07-28 12:04 am (UTC)