Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Comments

top

The NSFW HTML Attribute

14cfr01 -- Is Safe For Work (273 comments)

I agree with you, that this is great for writers & readers of sites that already mark their content as not safe for work.

However, I haven't seen anyone point out this problem, which lends itself to other complaints slashdotters have had: Currently, some page writers put "NSFW" next to objectionable links. If NSFW moves to an HTML relationship value, then you won't have a visual cue that the author marks stuff as NSFW or not.

Even if the browser alerts you when you mouse-over an objectionable link, when you mouse-over a non-NSFW link, you won't see a cue to tell you if it's safe or if the author failed to mark it as NSFW. If you're at work and worried about these things, then you'll have to do the same as you do now: judge based on the rep of the site and such, and assume that any unmarked link might lead to racy content.

If you're forced to make that assumption, perhaps you should make it official. Make an HTML relationship value "ISFW" (Is Safe For Work). Then readers can assume that unmarked links are dangerous, that marked links are safe according to the author. The browser can report that the link is marked safe (say, through the pointer icon or through a tooltip).

Just a proposal, but I think it's important to point out that an absence of NSFW tags doesn't tell you if they've been used or not. You lose the visual info that you occasionally get now.

more than 7 years ago

Submissions

14cfr01 hasn't submitted any stories.

Journals

top

Launch

14cfr01 14cfr01 writes  |  more than 11 years ago

Please follow these steps.

  1. Prop geek upright, facing the wind.
  2. Give him enough line to hang himself.
  3. Make certain something blows. M$ Word is a good resource for hot air and getting a rise out of the geek.
  4. Keep line taught, then pull.
  5. Geek will rise. Keep him tied to ground, else he will be LOST.

Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...