A Plea for Sanity
Jun. 30th, 2005 09:09 pm![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png)
Given the vast number of posts in the lilspeak debate over the past day, I decided I might as well review community policy as it pertains to debates like this one. While our in-system children do have a definite take on it, I'm trying not to show partiality, unless anyone thinks their input would be particularly important.
However, I've seen people threatening to quit or leave the community, saying they feel they or their children aren't safe any more, etc. As regards community policy, and safety, there are a few things I should clear up.
1. The original 'just say no to lilspeak' post and its followups did not violate any community standards, though the 'morons on crack' remark, which was quoted from a post in another community with different rules, was admittedly pushing the envelope. Therefore, controversial or no, it was allowed to stay.
This community is not a safe place, in the traditional sense. What it is is an open place. Like the old DP list, it's a place where one can freely discuss any aspect of multiplicity, within reason and without censorship, and everyone is responsible for their own safety and well-being. "Within reason," in this case, means that the mods, some of whom remember the endless flamewars that DP often turned into, instituted rules against direct attacking and flaming of other posters. You can criticise an idea without criticising the person who came up with it.
If your in-system kids, children, littles, whatever, will get upset if someone disagrees with them or doesn't want them to write in lilspeak, then no, this is not a 'safe place' for them if you're defining it that way. The mods will crack down on people if they flame or openly attack, but not if they disagree. Children are as welcome to post as anyone else, but they don't get special treatment.
2. If you feel that you have been personally flamed/attacked/insulted, let the mods know (email is preferred) and we will review the post in question to see if it violates community standards. We don't always read every comment, and sometimes things get out of hand when we're not looking.
However, I've seen people threatening to quit or leave the community, saying they feel they or their children aren't safe any more, etc. As regards community policy, and safety, there are a few things I should clear up.
1. The original 'just say no to lilspeak' post and its followups did not violate any community standards, though the 'morons on crack' remark, which was quoted from a post in another community with different rules, was admittedly pushing the envelope. Therefore, controversial or no, it was allowed to stay.
This community is not a safe place, in the traditional sense. What it is is an open place. Like the old DP list, it's a place where one can freely discuss any aspect of multiplicity, within reason and without censorship, and everyone is responsible for their own safety and well-being. "Within reason," in this case, means that the mods, some of whom remember the endless flamewars that DP often turned into, instituted rules against direct attacking and flaming of other posters. You can criticise an idea without criticising the person who came up with it.
If your in-system kids, children, littles, whatever, will get upset if someone disagrees with them or doesn't want them to write in lilspeak, then no, this is not a 'safe place' for them if you're defining it that way. The mods will crack down on people if they flame or openly attack, but not if they disagree. Children are as welcome to post as anyone else, but they don't get special treatment.
2. If you feel that you have been personally flamed/attacked/insulted, let the mods know (email is preferred) and we will review the post in question to see if it violates community standards. We don't always read every comment, and sometimes things get out of hand when we're not looking.
no subject
Date: 2005-07-01 04:09 pm (UTC)