That's cool--comments on old and new are always welcome! :D
Putting up the het and slash warnings was one of the many decisions we made when opening the archive that, upon later reconsideration, didn't really communicate what we wanted it to. We wanted people to be able to find and avoid stories with content they liked/didn't like; we didn't want anyone to be able to have an excuse to snark at authors for the "indignity" of having read a chapter only to discover it belonged to a "slash" story. (Or a het story, since there are rabid anti-het readers too.) I'm just sorry it took us as long as it did to get around to carrying out our intentions.
I'm with you on the "no slash" archives. While I recognize the right of archive owners to allow whatever they want, I also recognize my right to avoid sites that treat the relationships of dear friends and family as aberrations unworthy of exploring in literature.
![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2010-12-16 01:52 pm (UTC)Putting up the het and slash warnings was one of the many decisions we made when opening the archive that, upon later reconsideration, didn't really communicate what we wanted it to. We wanted people to be able to find and avoid stories with content they liked/didn't like; we didn't want anyone to be able to have an excuse to snark at authors for the "indignity" of having read a chapter only to discover it belonged to a "slash" story. (Or a het story, since there are rabid anti-het readers too.) I'm just sorry it took us as long as it did to get around to carrying out our intentions.
I'm with you on the "no slash" archives. While I recognize the right of archive owners to allow whatever they want, I also recognize my right to avoid sites that treat the relationships of dear friends and family as aberrations unworthy of exploring in literature.