Hacker News new | past | comments | ask | show | jobs | submit login

Good to know that Wikipedia contributors/editors have a healthy respect for their users! /s



Yes, we think if they go to an encyclopedia they're after encyclopedic content. It turns out Wikipedia isn't Ain't It Cool.


> we think

There's your problem. Your attitude consists of:

  We think that the users want X. A bunch of users have
  been asking for Y, but we are going to ignore them because
  what "we think" the users want trumps what actual
  users are asking for. Oh, and the users that don't like
  our attitude are "whiny."
You are not pointing to anything concrete about what your actual users want other than what you think your "ideal user" wants. Idealized views of what users want don't always end up matching reality.

Also, I'm failing to see how splitting information between "spoiler-full" and "spoiler-free" makes your content less encyclopedic, or has any link to Ain't It Cool News.

Overall, your general attitude of putting people down[1][2][3] represents Wikipedia in a poor light, represents yourself in a poor light, and generally comes across as very trollish.

[1] Splitting information into 'spoiler/no-spoiler' means that Wikipedia is going to turn into Ain't It Cool.

[2] Putting information behind a spoiler warning causes the content to be less encyclopedic.

[3] The spoiler hiding/warning is 'whiny' (and by extension it's proponents that don't want stories to be spoiled are also whiny).


The key problems were:

1. spoilers are inherently opinion - there is no way to dictate neutrally what is and isn't a spoiler, and no referenceable source for such

2. spoilers were superfluous in many cases (a section labeled "Plot" or "Summary" is going to have details of the story in it)

3. a spoiler-warning culture was causing editorial problems: relevant information being removed from articles for being a spoiler, or articles being twisted into weird shapes to herd details into "spoiler" sections

4. the spoiler culture was getting gibberingly stupid (a spoiler warning on "Romeo and Juliet" and "The Three Little Pigs", I shit you not).

The thing I did was remove several thousand spoiler warnings from "Plot" or "Summary" sections, where they were superfluous. When those were gone, the other problems were enough for consensus to reach the death of the spoiler warning.

But let's assume spoiler warnings are a great idea. How would you implement 1. neutrally and verifiably in a manner that was hard to argue with?


1. In the example at hand, a possible solution would be to separate the mechanics of how the episodes aired from the content of the story itself. You don't need story details to have an explanation of how Season 5 of Breaking Bad was broken into two pieces that aired a year apart from each other.

2. The fact that a major character dies, is pretty arguably a spoiler. Obviously not for stories so common and/or old that they are tropes (e.g. Romeo and Juliet). Coming back to the example of Breaking Bad Season 5, knowing that a major character dies is probably universally accepted as a spoiler within the first year or so after it airs.


So how far do you go back? And for what countries and, indeed, cultures? Note that English Wikipedia is not American Wikipedia, but pretty much International Wikipedia. The world is a very big place. You still seem to be assuming I've asked you for "something obviously acceptable people like me", and that's not the case at all. What's a rule for people who are from somewhere that couldn't even tell you who Baba Yaga was, let alone a story about her?


And if you're sure there's pent-up demand for such a thing, look to duskwuff's suggestion:

https://news.ycombinator.com/item?id=6709137

Construct the database, put a useful mechanism on it, crowdsource contributions, sell ads. HN is about doing stuff, after all.

(This is also more likely to achieve your desired result of a usable spoiler mechanism for Wikipedia.)




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: