This is something we already do, yeah. It hasn't been widely adopted yet, but it's a thing. Urinetown is an example.
I'm kind of against this, really. What may be a spoiler in one work, might not be a spoiler in another work.
If we did it, it would lead to all kinds of inconsistent sorting, which we probably be worse for us than any current problems.
edited 27th May '11 11:47:23 AM by TotemicHero
Expergiscēre cras, medior quam hodie. (Awaken tomorrow, better than today.)Consensus has suggested this, even though I don't like it. Honestly, if I haven't read/seen a work yet, and care at all about spoilers, it's probably not advisable to go tearing through the trope list. But that's just my opinion.
"It's Occam's Shuriken! If the answer is elusive, never rule out ninjas!"![]()
That's my point. If a trope is sorted in a certain way on page X, I'd expect it to be sorted the same way on other pages too.
In case people haven't noticed yet, I'm a big fan of all pages following the same basic format. This...kind of flies in the face of that style of consistency.
Expergiscēre cras, medior quam hodie. (Awaken tomorrow, better than today.)![]()
Well, I frequently use TV Tropes to find out whether I want to learn more about the work at all. Auto-spoilers are very, very annoying.
edited 27th May '11 11:56:50 AM by dryunya
TheOtherWiki could really use Laconic entries.I, also, tend to read a trope list to see what kind of tropes are present before I decide whether or not to read a work. I find spoilers annoying as well. I strongly favor the "cluster spoiler tropes under a folder at the bottom" approach.
Fight smart, not fair.Not sure why setting spoiler default as hidden in your profile and then not highlighting them wouldn't work just as well. Then again, I don't really mind spoilers.
Again, I don't agree with it, but consensus is consensus. Would be nice if someone could link the thread/crowner where this was decided, though.
Expergiscēre cras, medior quam hodie. (Awaken tomorrow, better than today.)I agree with Totemic Hero. I sometimes glance a trope list before reading/watch/playing some work (or while I am reading/watch/playing said work) and don't mind, at all, spoiled tropes. I just don't highlight them.
Having them grouped and not hidden in the end or in a folder, aside of being unaesthetic (my opinion), makes me more likely to be spoiled in long runners. I sometimes want to read about something I've seem already, but that is a a spoiler for newcomers. If the spoilers were all grouped, I couldn't do so without accidentally seeing some spoiler I don't know about yet.
Furthermore, I also have the tendency to seek for a few specific spoilers (such as wanting to know if there is a Happy or Bitter Sweet Ending in a particularly depressing work). Again, I wouldn't be able to do so without also seeing spoilers I don't want to.
I Beg to differ about being less likely to see them, as I said.
About editing. First of all, this wiki is about readers, not editors. Rules are meant for the reader's convenience, not the edotor's. And, during the editing, most of the text is nearly unreadable, unless you are actively trying, due to the wiki coding, anyway. Personally, I've never had any problem with spoilers while editing.
Plus, there could be quite a lot of debate for whatever a trope should go on top or on the bottom, due to Late-Arrival Spoiler.
What do you mean by that?
edited 27th May '11 2:38:39 PM by chihuahua0
The debate on whats a spoiler and whats not thing open one folder (or say the pages with 10 or 15 folders or worse having 5 pages or so.) scroll down to the letter see its not there and add it but its on the page already in the spoiler folder.
Also another thing Anime/Manga works spoiler different things. Like if Anime and Manga are running concurrently people will spoiler the Manga examples so they don't spoil the Anime only crowd. (full tropes or bullet points.) Or spoiler things that haven't officially hit the US yet. Having a secondary spoiler code for that would be a big help for that though.
edited 27th May '11 3:01:00 PM by Raso
Sparkling and glittering! Jan-Ken-Pon!Agree that this is a bad idea. It will lead to duplication, as people simply won't read to the spoiler bit at the bottom before adding the trope. Or there will be endless flame wars about what is and isn't sufficiently spoilerific, which could only be avoided by endless lawyering over where to draw the line. After all - to some people, almost any information at all about the work becomes a spoiler, and to some, almost nothing really is. And there's many, many kinds of inbetween.
Really not at all impressed by this, and I hope it doesn't become policy.
edited 27th May '11 4:27:55 PM by CaissasDeathAngel
My name is Addy. Please call me that instead of my username.Yeah, there seem to be plenty of objections in this thread, including a mod.
Even if duplicates aren't a problem, whinging about what is and isn't a spoiler is impossible to avoid. It's a subjective concept and this requires an impossible objective definition (we get by okay on the Wiki at large, but that doesn't require segregating tropes as spoiler and non-spoiler).
edited 27th May '11 4:56:11 PM by CaissasDeathAngel
My name is Addy. Please call me that instead of my username.Given the lack of response to my question, I'm going to assume that said threads or crowners have vanished into the Twisting Nether.
Seeing as this issue seems to be pretty heavily divided, should we start a new crowner and settle this?
Expergiscēre cras, medior quam hodie. (Awaken tomorrow, better than today.)
Crown Description:
Should inherently spoiler tropes (Tropes where the very name of the trope is a spoiler for the work, like Bad Guy Wins or The Hero Dies) be grouped up at the bottom of work pages that they are spoilers for?

There's one thing that keeps bugging me: The tropes on work pages are generally alphabetized, and thus can easily be unwittingly calculated. Why don't we try grouping the spoiler tropes, for example, at the end of the page, or in a separate folder? I think such practice would improve the wiki a bit.
TheOtherWiki could really use Laconic entries.