Sunday Confessions January 16, 2011

This is a weekly meme started by yours truly as a way to get to share a bit about myself and also learning more about you. Sometimes its about books and book related topics and sometimes it's not. This is all in good fun and I would love it if you would participate. 

To Spoil or Not To Spoil. That's this weeks question.

This week's topic is something I struggle with all the time: Spoilers. I don't like them.  Whenever I read a review on another blog, if I haven't read the book, I usually just skip to their overall impression of the book. When I write reviews myself, I try my hardest not to include anything that might ruin the book for someone else. After all you can only read a book for the first time once.  If someone tells you all the good parts before you even start reading then there is no magic, no surprises. Of course if I've already read the book, I love reading reviews to see what others have thought about it. So now the question goes out to you.  Do you like spoilers? How much information do you like to see when reading a review?  I would love to know your thoughts on the subject.


  1. I am not a fan of spoilers and I had a bit of trouble when I first started reviewing with how to approach them so as not to give too much away. What I saw some bloggers do and what I do now is use white text so that you have to highlight it in order to read the spoilery information. That seems to work fairly well, and that way readers don't have to avoid my entire review in order not to be spoiled. It's a tricky thing, though, knowing just what is a spoiler and what isn't! I think it varies a lot depending on the person, so that's another thing to keep in mind.

    Good question! :)

    A Tapestry of Words

  2. Good question.

    I think that spoilers should be avoided in a review. The point of reviews is to highlight good aspects and bad aspects about a book, but that doesn't mean to highlight significant plot points.

    However, I am not bothered by reviews that contain spoilers, as long as they are clearly identified with a big bold "SPOILER!" right before it. That way I know to avoid it.


  3. You can read my Sunday Confessions here! :)

    Great question this week!

  4. I hate spoilers. I hate being told I need to read the Introduction to a book for school, and it gives everything away. Not cool! I think reviewers should have a "what you need to know" section that provides a general plot, and then go into details from there as to what the person thought of the book. Mentioning spoilers are coming is also a good way to avoid angry eyes from readers. :)

  5. I totally agree with you. I hate spoilers. I think they're okay if you write them in the same call as the book ground so you have to highlight it to read it [:

  6. I agree with you on no spoilers. I try my hardest not to use them.
    I sometimes reference the synopsis on the back of the book or the bookflaps because anyone who pulls the book off the shelf could see them.
    Or if I'm reviewing a history book I may include information that could be viewed as a spoiler, but my thoughts in that situation are that since it's about something that has already happened, it's no longer considered a spoiler. Especially since most of the history/historical fiction I read is based on Tudor England or the French and American Revolutions.

  7. No spoilers - or at least a warning so that people can chose whether they want to read it or not!

  8. We try to do the same on Reading Lark. If we have to include spoilers then we at least put a warning at the beginning.

    Our Sunday Confessions

  9. hello im a new follower=) and i just came across this meme im going to start using it on my blog!


Post a Comment