So please, it's very little effort to use spoiler codes. So please do so regardless of the book's age.
Oh, for Pete's sake!
--Sran
So please, it's very little effort to use spoiler codes. So please do so regardless of the book's age.
I would prefer a policy based in real data than an arbitrary guess at how long spoiler code should be used in this forum in order to protect readers from themselves.
Boil it down and my point is yours. Read TrekBBS defensively.
But you don't want spoilers after the book's release. How does one read defensively if this place is littered with uncoded spoilers, both deliberate and accidental?
The problem is the phrase "I shouldn't have to concern myself." We all should try to concern ourselves with other people's feelings. No, we shouldn't bend over backward to accommodate rabid spoilerphobes, but we shouldn't be completely inconsiderate about it either. Just because some reactions are unreasonable, that's no excuse to say "I'll act however I want and everyone else better stay out of my way."
Is that data real enough for you?
But you don't want spoilers after the book's release. How does one read defensively if this place is littered with uncoded spoilers, both deliberate and accidental?
By avoiding the message board in question altogether.
Oh, no. I'm not going to worry about other people's feelings when they are absolutely out of my control. No matter what we do, someone will feel something somewhere between irked and boiling mad, depending on their attitude, not mine. If I have to stop and think every time I post whether this or that tidbit will "spoil" something for someone, I'm not going to post anything interesting or with substance outside of a spoiler code. And if everything would have to be spoiler coded, then nothing is really spoiler coded.
We have to find a balance that works.
Oh course it's not hard to consider whether a particular plot point is "enough of a spoiler" to be in spoiler code. What's hard is deciding what isn't a spoiler for someone. The fact is, every detail can be considered a spoiler and is considered a spoiler by someone. The question is not "Should we be considerate of others?". The question is "How realistically considerate can we be before we're being ridiculous?"
It's not hard to think "Is this plot point enough of a spoiler that it should be in a spoiler code?". The latest book has a major spoiler released because the person who did it doesn't know how to use spoiler codes. I cannot speak for others who read that and now know a major plot point before reading the book. But something that big really should have been in a spoiler code.
We have to find a balance that works. We do have to take into account others and how they might feel.
Now I don't even know if there is anything that would constitute as a major spoiler in Trek lit so maybe this is a non-issue.
I was one of the people spoiled in that thread. But, as I posted in that thread, I entered at my own risk knowingly as it had *SPOILERS* in the title when I entered.
And the start time would be from the date of the eBook since that does have a fixed date that we can keep track of.
And the start time would be from the date of the eBook since that does have a fixed date that we can keep track of.
No, the start time will be whatever the mods decide it is, and the rest of us will abide by that.
--Sran
The date of release on the S&S website is the date of release of the eBook. That is why I chose that date because it's a fixed date and everyone then has a chance to have at least the same amount of time to read.
The date of release on the S&S website is the date of release of the eBook. That is why I chose that date because it's a fixed date and everyone then has a chance to have at least the same amount of time to read.
I understand why you chose the date. That's not the point. You're not the one who makes the rules around here. The mods do that. The six-month mark for each book is whatever they say it is.
--Sran
We use essential cookies to make this site work, and optional cookies to enhance your experience.