FANDOM


Forums > Senate Hall archive > SH Archive/Spoilers in the Quote of the Day

I know there are spoiler tags for the parts of articles that contain spoilers, and we have a list of pages to avoid. That seems like a good policy. In that same vein, I might suggest we either put spoiler tags around the quote of the day if it's from an upcoming album, or better yet, not use revealing quotes from upcoming media.

I was referencing that Cal Omas quote up today in particular, but not necessarily limited to that. Unsigned comment by Serendipitousus (talk • contribs).

  • Good idea. But the spoiler period for Legacy of the Force: Sacrifice is over. It's been out over 1 month. -Fnlayson 18:55, 7 July 2007 (UTC)
    • Can't get it where I live yet. the only shop i've seen which sells star wars books -other than movie novelizations- in ireland still hasn't got it. Tutos Lumenarious 21:06, 7 July 2007 (UTC)
  • See also our spoiler warning on the front page, above the quote box. Gonk (Gonk!) 21:24, 7 July 2007 (UTC)
  • Idaknow, I think spoilers of recent book series really should be left out of the QOTD. It will be a long time before some people read those books (myself included). At least wait until they're in paperback. - Graestan 21:26, 7 July 2007 (UTC)
    • Books are normally re-released in paperback a YEAR after they've been published in hardcover. Surely you're not suggesting we wait a year for QOTD? Din's Fire 997 23:46, 7 July 2007 (UTC)
      • Though I'm not going so far as to actually suggest it myself . . . are there so few good quotes for stuff that's been out for more than a year that we have to dip into the recent stuff? jSarek 01:48, 8 July 2007 (UTC)
        • Methinks that year estimate is a tad exaggerated. I got the Rise of Darth Vader paperback less then six months after the hardcover was released. But anyway...back on topic...yes, we should avoid spoilers in the QOTD - there is plenty of non-spoiler material that is as yet untapped.--Goodwood 01:46, 9 July 2007 (UTC)

I'm not saying I don't agree that there is a lot of good stuff already out there. I'm just saying QOTD shouldn't have a time delay. Besides, assuming a quote is nominated, passed, and added to the que all on the day of release, it likely won't make the main page until long after the one-month spoiler limet is over anyway. Din's Fire 997 07:03, 9 July 2007 (UTC)

  • Speaking as someone who hasn't read Sacrifice, I don't see much in that Cal Omas quote that gives away anything. OK, the leader of the Republic, or Legacy equivalent, has been arrested. Major shakeup, granted, and intriguing, but the quote doesn't indicate by whom or why. And it certainly doesn't reveal any of the Big Spoilers of the novel. But for what it's worth, if there's a genuinely big spoiler in a quote nominee, I'll vote against it, and I probably won't be the only one. Enochf 08:41, 9 July 2007 (UTC)
  • You could argue that depending upon anyone's level of knowledge in the universe, any quote or featured article could potentially lead to a "spoiler". There's no real way to guard against it. I agree that there should be a couple of weeks or two-three month window for quotes that come from new sources. Beyond that, the entire site is technically up to the reader/viewer's discretion. They should know "what they're getting into" from the beginning. Jedi Master Fiolli 15:22, 13 July 2007 (UTC)
    • Per Fiolli. That's why we have the "Warning: Spoilers" alert on the main page (per Gonk, as well). Besides, it's not like the quotes don't go through the voting process, and a random spoilerific quote could just be put up there by some random user (which, I suppose, is per Enochf). Is that saying that "Luke... I am your father" can never be a QOTD, because it's a huge spoiler for the original trilogy? Who knows whose seen what? JorrelWiki-shrinkableFraajic 04:34, 26 February 2008 (UTC)

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.