Voting Discussion: We're Screwing In Light Bulbs AIFG!
We open it up, we talks the talk, we votes, we shuts it down. This thread is to free up Bureaucracy for daily details as we hammer out the Big Issues towards a vote. Open only when a proposal has been made and seconded according to Buffista policy (Which we voted on!). If this thread is closed, hie thee to Bureaucracy instead!
Right, it's a POSSIBLE spoiler, hence the curtosey of asking someone to put a freakin "s" and a freaking "return".
Staying way the heck out of the flamage, but I find it hard to read a thread when every other sentence is whitefonted, thus my complete skimming of Spoilers Light.
I'm all for letting the vote decide after hearing viewpoints, I just wanted to bring up the legibility issue as part of the debate. Bugging off now until people are calmer.
Staying way the heck out of the flamage, but I find it hard to read a thread when every other sentence is whitefonted, thus my complete skimming of Spoilers Light.
Would you like a beer, thessaly? You know, just since I'm right there with ya.
Staying way the heck out of the flamage, but I find it hard to read a thread when every other sentence is whitefonted, thus my complete skimming of Spoilers Light.
I'll be at the bar with thessaly and Gandalfe.
Would you like a beer, thessaly? You know, just since I'm right there with ya.
Foamy!
ION, as a very abstract idea that wouldn't happen anytime soon because it involves coding that would be behind everything else, how hard would it be to have a spoiler tag that interacts with a user setting to be visible/blinvisible? Then the Hos could view with impunity and the Virgins could not view with impunity.
Again: please do not let the coders hurt me. I know this won't happen in this round of debates, just an idea for a future feature that might be nice.
how hard would it be to have a spoiler tag that interacts with a user setting to be visible/blinvisible? Then the Hos could view with impunity and the Virgins could not view with impunity.
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.
Edit: does this mean no beer?
how hard would it be to have a spoiler tag that interacts with a user setting
thessaly, I don't know all the details of how this particular board is coded, but in a perfect world, that kind of reader-sensitive tag shouldn't be that much worse to code than a MARCIE (which also says "ita wants to see X, but Plei doesn't", in effect.)
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.
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.