Brent Dax (brentdax) wrote in suggestions,
Brent Dax
brentdax
suggestions

Adult content warnings should respect existing cut tags

Title
Adult content warnings should respect existing cut tags

Short, concise description of the idea
Posts which already have a cut tag should not be completely hidden if they are marked as having adult concepts or content; instead, they should be rendered as normal, with the warning page appearing between the cut and the full post.

Full description of the idea
Responsible posters have long protected adult content behind LJ cuts; besides providing some protection against minors, this is a simple courtesy for people who may be browsing at work, school, or in a public place, or who may not wish to view individual posts which aren't to their taste. People posting like this will generally have a work-safe description of the contents outside the cut, allowing readers to make an educated decision about whether they want to view the content or not.

As currently implemented, the adult content and adult concepts warnings don't play well with this practice. They forcibly wrap all the content in a cut that gives no indication of what's underneath. Clicking on the cut then leads to a warning page, which again gives no indication of what sort of content is being protected, just that for some unspecified reason it isn't appropriate for all audiences. While this is certainly "safe", it's also less user-friendly.

What I propose is that the forced replacement not be performed on posts which already contain a cut tag. (The author-created cut tag should still lead to a warning page; this serves an important function for e.g. parents sitting within eyeshot of the computer.) This would allow authors who use cut tags to provide a better reader experience, while still protecting users from accidentally viewing objectionable content posted by careless authors.

One issue is that malicious authors may try to circumvent the protection by deliberately inserting a cut tag that doesn't cover the objectionable content. This clearly is a misuse of the system, and the abuse team should have a way to restore the default (forced-cut) behavior on such posts.

An ordered list of benefits
  • Readers will have more information about why content may be inappropriate for some audiences
  • Readers can make an informed decision about whether protected content is right for them
  • Userbase will be less annoyed by adult content protection system
An ordered list of problems/issues involved
  • Authors could attempt to circumvent protection by inserting cuts that don't cover objectionable content
  • Combatting this practice could take more abuse team time
Tags: adult content, lj-specific markup, § no status
Subscribe
  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

  • 17 comments