opposing this as an abstract idea. I would prolly turn off whitefont if that were an option, but I'd rather not have to read the movies thread with my eyes shut.

If there were a thread-by-thread whitefont option, that would be pretty cool.

Again with the "Please Almighty Coders Whose Works I Am Not Fit to Debug, No Pressure!", but here's how the structure plays out in my head (YHeadMV):

- In the user's Profile, there would be checkboxes, either listed at the end of the page or under the thread subscriptions. Checking/unchecking a box would create a cookie.

- A tag similar to the current spoiler tag would white out text after checking the user's cookie. I'm not sure whether or not the current code could be altered slightly to do this.

- The code for this could be repurposed to make separate tags (same code, different shortcut), for instance, a casting-only tag, a general tag that could be used for Literary/Movies/etc., a seekrit tag for sending Seekrit Messages in Natter or Bitches, a CompleteHo tag for me.

The problems I see are making sure that the shortcuts are easy and that there aren't so many of them we have to create our own spoiler ++ language to accomodate them.

This would, however, solve the problems of both Virgins & Hos by making the information available based on user preference.

Focus group at noon.

More beer?

More beer?

Please.

Then bed.

When will this one go to a vote, BTW?

Hmm. See, there's white font I'd avoid (movie endings, book discussions, blah blah blah), and I don't think I'm the only one.

Even if possible, it's not *practical*.

And it shouldn't be needed.

The problem I see with it is that you'd be entirely dependent on writers tagging their posts properly -- so you'd be compounding the usual "does this belong in the spoiler thread?" dilemma with newbies not reading the quick-edit instructions, people not closing tags properly, different levels of sensitivity, and so on.

Good point - although admins could also fix stuff as now (blame my former!Stompy husband, I don't want add Stompy Workload).

Another idea (I've mentioned it to DX) would be to create a "Preview Post" button next to "Post Message" that would display the post in a pop-up window, making it easier to see when there is a problem at the user level before it's posted for real.

As a general rule, I would recommend a 'if in doubt, use the all-purpose tag' to help simplify the process for newbies, but I'm confused by the current policy to the point of not posting (and I imagine some newbies are as well), so being confused with better options and an easier reading environment works for me.

Hmm. See, there's white font I'd avoid (movie endings, book discussions, blah blah blah), and I don't think I'm the only one.

There would still be a general catch-all whitefont (probably the s tag would remain the same).

Even if possible, it's not *practical*.

This may be true, and even if it is, the UI & guidelines would really need to be worked out carefully to not be a PITA. It just seems to me a possible way to accomodate both sides. At any rate, I've drifted from the topic at hand into design, so I'll stop unless someone wants to bat this around in BBB.

Ok. One last bit.

Victor has just summed up this idea as:

See or not see by cookie, it's good enough for me.

Please send beer. Or valium.

And it shouldn't be needed

Hey, I'm also tired of being told how I should feel about the shows.

See or not see by cookie, it's good enough for me.

I have no clue if this is a possibility, but I think the idea rocks.

Trudy, how is a TV movie a spoiler about a show that just started filming this week?

That post didn't have just the TV movie description in it. It had a flatly stated casting spoiler. The problem of the unclear description of the movie just compounded things, but it wasn't the main issue.