You know what's odd about Mobile read? - Page 3

FizzyWater · 03-16-2018, 07:19 PM

I think you'll run into problems with what people consider spoilers. And how long they want them to apply. In the old days when I belonged to various Yahoo groups, we tended to limit spoilers to the first month after a book was released. I've had people growl at me here if I commented too freely on a 10 year old book.

crich70 · 03-16-2018, 07:39 PM

Quote:

Originally Posted by dordale

I'd prefer to have reviewers use "spoiler" tags if their reviews contained such. I sometimes like to read reviews to get ideas for books or to help me decide if a book I'm thinking about would be right for me. If I didn't know whether a review contained spoilers or not it would keep me from using the reviews posted. I suspect this would be the case for others as well.

What you're referring to is more a book discussion thread--something I see as being different from a review thread. I'd join a discussion threat to discuss my feelings about a book after reading it, I read through a review thread to get other peoples' opinions to help decide if I want to read the book or not.

I agree. If I read a review it's likely because I want to get an idea if a given book is one I would enjoy reading or not. So I wouldn't want plot points being given away before hand. And I think that the reason for reading a review is to see if it is worth spending my $ on or not. No one wants to buy junk after all. We all want to get our money's worth when we buy something. That's why people read reviews and look at customer feedback for places like Amazon and Ebay. To see if the product is likely to be worth their time and money or not.

Thasaidon · 03-16-2018, 10:00 PM

If threads were limited to one book then "Includes Spoilers' could be put in the thread title.

This would allow those who did not want to risk seeing the spoilers to avoid threads which have reviews containing spoilers.

DuckieTigger · 03-17-2018, 12:52 AM

Quote:

Originally Posted by FizzyWater

I think you'll run into problems with what people consider spoilers.

Ah yes. Without going into detail a book review is always going to spoil it somewhere. Otherwise a spoiler free review is indistinguishable from the next. I believe a review is supposed to be more than just a blurp.

4691mls · 03-17-2018, 08:29 PM

Quote:

Originally Posted by dordale

I'd prefer to have reviewers use "spoiler" tags if their reviews contained such. I sometimes like to read reviews to get ideas for books or to help me decide if a book I'm thinking about would be right for me. If I didn't know whether a review contained spoilers or not it would keep me from using the reviews posted. I suspect this would be the case for others as well.

What you're referring to is more a book discussion thread--something I see as being different from a review thread. I'd join a discussion threat to discuss my feelings about a book after reading it, I read through a review thread to get other peoples' opinions to help decide if I want to read the book or not.

I agree - a discussion thread is different from a review. It is possible to post a review that doesn't give away plot points beyond what's in the book blurb. The reviewer can say whether or not he/she thought the book was well written, entertaining, thought-provoking, full of errors, fast-paced, slow-moving, etc.

Tarana · 04-09-2018, 02:32 PM

Honestly, I avoid book reviews because they have too many spoilers today. I prefer the short "I liked it because ..." or " I didn't like it because...." or simply "it wasn't my cup of tea."

Pulpmeister · 04-11-2018, 12:48 AM

Mostly, when I post a discussion or review of a book here, it's a very old book. Such as "Seven Days to Never", 1956. Or the Count of Monte Cristo, 150 years old. Spoiler time is over.

Like discussing Genesis (Spoiler alert: Adam and Eve unhappy ending.)

GlenBarrington · 04-11-2018, 07:36 AM

Quote:

Originally Posted by Pulpmeister

Mostly, when I post a discussion or review of a book here, it's a very old book. Such as "Seven Days to Never", 1956. Or the Count of Monte Cristo, 150 years old. Spoiler time is over.

Like discussing Genesis (Spoiler alert: Adam and Eve unhappy ending.)

What? Ahhh Drat!

issybird · 04-11-2018, 08:20 AM

Quote:

Originally Posted by Pulpmeister

Mostly, when I post a discussion or review of a book here, it's a very old book. Such as "Seven Days to Never", 1956. Or the Count of Monte Cristo, 150 years old. Spoiler time is over.

Yep. Rosebud is a sled, To Serve Man is a cookbook, and "OMG, it's the Statue of Liberty buried up to her oxters!"

That said, for recentish stuff it's good when a review starts with generalities so you can cut yourself off in time. The issue is where you draw the recentish line.

Catlady · 04-11-2018, 09:42 AM

Quote:

Originally Posted by issybird

Yep. Rosebud is a sled, To Serve Man is a cookbook, and "OMG, it's the Statue of Liberty buried up to her oxters!"

That said, for recentish stuff it's good when a review starts with generalities so you can cut yourself off in time. The issue is where you draw the recentish line.

But even the old stuff is new to some people. Giving away endings is a no-no in my book, regardless of how old or well-known something is.

4691mls · 04-11-2018, 09:48 AM

I doubt we'd ever reach a board consensus on how new is "recentish", but no matter the age of the book it shouldn't be a hardship for a reviewer to type the word "SPOILERS" as a warning if it applies.

I would probably assume any subsequent posts/discussion by other people might go into more detail/spoilers, but it would be nice to know whether the initial review contained spoilers.

jhowell · 04-11-2018, 10:18 AM

Quote:

Originally Posted by issybird

Yep. Rosebud is a ....

Really not cool! Please don't blurt out the endings to classics in random threads.

Those are all new to someone.

issybird · 04-11-2018, 10:22 AM

Quote:

Originally Posted by jhowell

Really not cool! Those are all new to someone.

Since I didn't identify the works in question, I figured it was safe. If people want to google the references, that's their lookout.

jhowell · 04-11-2018, 10:24 AM

Quote:

Originally Posted by issybird

Since I didn't identify the works in question, I figured it was safe. If people want to google the references, that's their lookout.

I picture someone sitting down to watch a classic film and then realizing, "So that's what she meant!"

doubleshuffle · 04-11-2018, 10:36 AM

But seriously, if you can't enjoy that film knowing what Rosebud is, you should be watching Transformers anyway.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Hello, Mobile Read!	tinder_box	Introduce Yourself	4	01-24-2012 09:12 AM
New to mobile read	scot38	Introduce Yourself	6	03-17-2011 02:01 AM
A Mobile Read 'Essential Books to Read' list	ficbot	Reading Recommendations	41	09-24-2010 10:31 AM
New to Mobile Read	skern922	Introduce Yourself	3	12-23-2009 06:53 AM
What books from Mobile Read have you read?	ficbot	Reading Recommendations	29	08-01-2009 05:39 PM

03-16-2018, 07:19 PM	#31
FizzyWater You kids get off my lawn! Posts: 4,220 Karma: 73492664 Join Date: Aug 2007 Location: Columbus, Ohio Device: Oasis 2 and Libra H2O and half a dozen older models I can't let go of	I think you'll run into problems with what people consider spoilers. And how long they want them to apply. In the old days when I belonged to various Yahoo groups, we tended to limit spoilers to the first month after a book was released. I've had people growl at me here if I commented too freely on a 10 year old book.

03-16-2018, 10:00 PM	#33
Thasaidon Hedge Wizard Posts: 800 Karma: 19999999 Join Date: May 2011 Location: UK/Philippines Device: Kobo Touch, Nook Simple	If threads were limited to one book then "Includes Spoilers' could be put in the thread title. This would allow those who did not want to risk seeing the spoilers to avoid threads which have reviews containing spoilers.

04-09-2018, 02:32 PM	#36
Tarana Wizard Posts: 3,980 Karma: 38840460 Join Date: Sep 2012 Location: Minneapolis Device: PWSE, Voyage, K3, HDX, KBasic 7 & 8, Nook Glo3, Echos, Nanos	Honestly, I avoid book reviews because they have too many spoilers today. I prefer the short "I liked it because ..." or " I didn't like it because...." or simply "it wasn't my cup of tea."

04-11-2018, 12:48 AM	#37
Pulpmeister Wizard Posts: 2,502 Karma: 28893796 Join Date: Nov 2011 Location: Perth Western Australia Device: kindle	Mostly, when I post a discussion or review of a book here, it's a very old book. Such as "Seven Days to Never", 1956. Or the Count of Monte Cristo, 150 years old. Spoiler time is over. Like discussing Genesis (Spoiler alert: Adam and Eve unhappy ending.)

04-11-2018, 09:48 AM	#41
4691mls Wizard Posts: 2,776 Karma: 30081762 Join Date: Jan 2012 Location: US Device: ALL DEVICES ARE STOCK: Kobo Clara, Tolino Shine 2, Sony PRS-T3, T1	I doubt we'd ever reach a board consensus on how new is "recentish", but no matter the age of the book it shouldn't be a hardship for a reviewer to type the word "SPOILERS" as a warning if it applies. I would probably assume any subsequent posts/discussion by other people might go into more detail/spoilers, but it would be nice to know whether the initial review contained spoilers.

04-11-2018, 10:36 AM	#45
doubleshuffle Unicycle Daredevil Posts: 13,923 Karma: 185041098 Join Date: Jan 2011 Location: Planet of the Pudding Brains Device: Aura HD (R.I.P. After six years the USB socket died.) tolino shine 3	But seriously, if you can't enjoy that film knowing what Rosebud is, you should be watching Transformers anyway.

Advert

Advert