You're never going to get everyone to agree about such things. So you can either give up on any and all efforts to implement a sweeping spoiler rule, or accept an absolute minimum rule.
I'm not arguing with you, honest. Just stating what should be blindingly obvious by now after all these pages of repeating the same arguments.You're never going to get everyone to agree about such things. So you can either give up on any and all efforts to implement a sweeping spoiler rule, or accept an absolute minimum rule.
That's been precisely my point, though. Not everyone has to agree. The mods run this site. Whatever they decide is what goes. Anyone who doesn't like what they decide can leave.
--Sran
Watching the Clock came out more than 2 years ago - I'd say that at this point, any "spoilers" from that book are fair game.
Watching the Clock came out more than 2 years ago - I'd say that at this point, any "spoilers" from that book are fair game.
I've been giving this some thought.
I'd say if a book 2 years old is 'spoiled' for you, that's just tough.
These threads are for enthusiasts and the majority read the novels soon after release. Six months seems fair with a decent leeway built in.
If you are over six months behind, put up with spoilers, catch up or stay out of the Literature threads. Otherwise you are expecting everyone to jump through hoops for your benefit.
If it's that old then it's fair game in any thread. It's easiest for everybody if we just have one uniform rule for every book and every thread. In situations like this it really is best if the rules are simple and uniform across the board. If things in a thread about a specific book don't need to be spoiler coded in that book's threads, then they shouldn't need to be spoiler coded in any threads.
That's been precisely my point, though. Not everyone has to agree. The mods run this site. Whatever they decide is what goes. Anyone who doesn't like what they decide can leave.
--Sran
Watching the Clock came out more than 2 years ago - I'd say that at this point, any "spoilers" from that book are fair game.
I've been giving this some thought.
I'd say if a book 2 years old is 'spoiled' for you, that's just tough.
I think this is a fallacious argument. If the members of this forum make up even 1% of the total market for TrekLit, it's already doomed.Yeah I get the message. "Frak off loser, you're not wanted here. Read quicker." That's why I pretty much left.
Interestingly enough that plus my big backlog of stuff to read has meant I've also pretty much stopped picking up the books too. When you're part of the community, when you engage with the authors, you tend to care more, you pick up to keep the line going and the authors supplied with gin.
You guys are aware that the line can't survive on just you few elites that can read books within 6 months (or even 1 or 2 years) of publication right? You're aware that by driving us from the community you're effectively killing the line right?
Because honestly, in a couple of years when they junk and reset the whole shared universe thing (you've seen the writing on the wall), it'll be your fault for attempting to drive away 90% of the audience for those books.
Just suggesting there be a 'don't be a prat' rule.
Yeah I get the message. "Frak off loser, you're not wanted here. Read quicker." That's why I pretty much left.
You're aware that we're a subset within a subset, right? If every person in the LIT forum quit Star Trek tomorrow, the publisher wouldn't even notice.You guys are aware that the line can't survive on just you few elites that can read books within 6 months (or even 1 or 2 years) of publication right? You're aware that by driving us from the community you're effectively killing the line right?
Because honestly, in a couple of years when they junk and reset the whole shared universe thing (you've seen the writing on the wall), it'll be your fault for attempting to drive away 90% of the audience for those books.
What I'm trying to is to clarify if it's OK or not to spoil a book not mentioned in the thread title. You've read or not the book in the topic and go into the thread and it the title does say (Spoilers!). But it doesn't say (Spoilers!) for a different book. So any spoilers for a different book should be in spoiler codes as that's not what's expected in the thread.
In the thread about The Fall: Revelation and Dust is a spoiler for DTI: Watching the Clock that is not using a spoiler code and then it gets quoted a few times. So it's rather difficult to avoid the spoiler for the book that should not have been spoiled in a thread about a different book. If you want to spoil a book, start a thread for it.
This is not an extreme reaction. It's perfectly logical. If a thread is on book a, don't then spoil book b. That (IMHO) is rude.
Watching the Clock came out more than 2 years ago - I'd say that at this point, any "spoilers" from that book are fair game.
I've been giving this some thought.
I'd say if a book 2 years old is 'spoiled' for you, that's just tough.
Yeah I get the message. "Frak off loser, you're not wanted here. Read quicker." That's why I pretty much left.
I'm the one that mentioned DTI: Watching The Clock in that thread. First, while it is an event that took place within the book, that particular instance was one small thread and while entertaining, doesn't affect the over all story. A fact you would know if you actually read the book.
I'm the one that mentioned DTI: Watching The Clock in that thread. First, while it is an event that took place within the book, that particular instance was one small thread and while entertaining, doesn't affect the over all story. A fact you would know if you actually read the book.
But for those that have not yet read the book, they don't know that's a small spoiler. It does sound possible to be a big spoiler. You should be looking at thing from the point of view of someone who has not read the book and maybe any of the books following.
The thing is, we do get people coming here asking what to read/where to start reading. So those people are not caught up. There are people who prefer to read a series in it's entirety whenever possible and maybe The Fall is something they are waiting to be finished before starting it. So while the first book could easily become more then six months old for these people, it's new to them and spoiling book one because you can is just wrong (IMHO).
The way it's been until the latest book has been that spoiler codes have been used for proper spoilers. So, someone that has been keeping up here would think that would be the same for the latest book. But no, someone had to go and botch that. I know the book's thread has (Spoilers!) in this, but still, I don't feel that revealing a major plot point out in the open is appropriate. As it's been, anytime I've read a big enough spoiler for a new book, it's been at my doing, not because someone doesn't know how to use spoiler codes. And even if we did manage to go past the message's spoiler, others went to let it go out in the open with NO WARNING! That to me is rather rude.
So please, be careful with spoilers and spoiler codes regardless of a book's age. If you started the thread and big enough spoilers do get loose, go back to your original thread and edit it to say so or get a moderator to do so. Then it won't be an issue. Because as long as the 1st message has not spoilers and does warn that there are spoilers, then you are OK.
All it takes is two mouse clicks to get to the spoiler dialog.
All it takes is two mouse clicks to get to the spoiler dialog.
I think most people here are intelligent enough not to post spoilers without warning in a thread asking about reading something, or if the OP has made it clear they have not read all of the book. I've been here for a while now, and other than the occaisional mistake I don't remember coming across any cases of someone just purposefully posting spoilers. It might have happened, but not often enough for me to remember, which means it probably it's even common enough to be that it would call for a change in spoiler policy.I'm the one that mentioned DTI: Watching The Clock in that thread. First, while it is an event that took place within the book, that particular instance was one small thread and while entertaining, doesn't affect the over all story. A fact you would know if you actually read the book.
But for those that have not yet read the book, they don't know that's a small spoiler. It does sound possible to be a big spoiler. You should be looking at thing from the point of view of someone who has not read the book and maybe any of the books following.
The thing is, we do get people coming here asking what to read/where to start reading. So those people are not caught up. There are people who prefer to read a series in it's entirety whenever possible and maybe The Fall is something they are waiting to be finished before starting it. So while the first book could easily become more then six months old for these people, it's new to them and spoiling book one because you can is just wrong (IMHO).
Honestly, I'm behind by at least a year or too (the most recent book I have read is Raise the Dawn) and I am aware of the presence of spoilers, and I don't care about them. But I really don't see where it would be that hard to remain relatively spoiler free if I wanted to be. If you want to avoid spoilers you just need to be careful and watch what threads you go into.The way it's been until the latest book has been that spoiler codes have been used for proper spoilers. So, someone that has been keeping up here would think that would be the same for the latest book. But no, someone had to go and botch that. I know the book's thread has (Spoilers!) in this, but still, I don't feel that revealing a major plot point out in the open is appropriate. As it's been, anytime I've read a big enough spoiler for a new book, it's been at my doing, not because someone doesn't know how to use spoiler codes. And even if we did manage to go past the message's spoiler, others went to let it go out in the open with NO WARNING! That to me is rather rude.
So please, be careful with spoilers and spoiler codes regardless of a book's age. If you started the thread and big enough spoilers do get loose, go back to your original thread and edit it to say so or get a moderator to do so. Then it won't be an issue. Because as long as the 1st message has not spoilers and does warn that there are spoilers, then you are OK.As long as it's a spoiler thread, then you have then you really can't criticize some for posting spoilers.
All it takes is two mouse clicks to get to the spoiler dialog.
I've been here for a while now, and other than the occaisional mistake I don't remember coming across any cases of someone just purposefully posting spoilers. It might have happened, but not often enough for me to remember...
All it takes is two mouse clicks to get to the spoiler dialog.
And all it takes is no mouse clicks to not look at novel thread. Seriously, shut the hell up already!
--Sran
There have certainly been a few incidents over the years, in which someone mentions they have yet to read a certain older book, and is it worth reading, and people jump in and spill all the contents, then defend themselves by saying that it's "an old book".
Just suggesting there be a 'don't be a prat' rule.
Don't be a Prat is a good life rule in general, do we really need to formally document it? And if someone decides to ignore it, does a warning on a message board really deter them? We can create rules until it's impossible to interact at all here, but why? And for whatever rule/length of time you choose, there's someone further behind than you, so even when you eventually catch up, you can't discuss the book either...
To be honest, that's basically how it used to be without any policing anyway. My problem with this formal 6 month policy (and I'm not sure where that came from) is that previously, if someone spoiled something big, someone would report the post and a mod could drop a note to the user asking them not to do that and spoiler code that out. It seems that now this won't happen, as it isn't breaking the rules - and I remember seeing a mod defense of having a certain DS9 spoiler in a thread title, which is when I gave up on the board.
The majority of people here are capable of just being sensible and considerate about this, but there's a couple, some on this thread, that have made it quite clear that they'll only do something when told to by a mod, and if the mod says you can spoil with impunity anything older than six months, then they'll jolly well do that and who the hell are you to ask them to do otherwise.
We use essential cookies to make this site work, and optional cookies to enhance your experience.