Kindle Copyright Woes, Take 2

by Joshua Auriemma on March 1, 2009

44968129For those of you who haven’t been following the Kindle 2 copyright problems, essentially publishers (and authors?) have been complaining about the text to speech feature of the new Kindle.  Their claim is that including a text to speech engine is a violation of their rights as copyright holders under § 106 of the Copyright Act.  From what I gather, their argument is that the audio reading could be a derivative work.

While there seems to be some good fair use arguments — in particular, it should be pointed out that text to speech software can in no way compare to a real dramatic reading — Amazon has disappointed me by backing down from the feature.  In its new form, publishers will be able to elect whether or not their a book will be available to the Kindle text to speech feature.  Better than nothing, I suppose.

You make me sad, Amazon.

Incoming search terms:

  • kindle copyright
  • kindle free com copyright problems
  • kindle effect copyright
  • kindle copyright obtaining
  • kindle copyright detection
  • copyright kindle
  • how copyright work on kindle
  • how can kindle effects copyright
  • copyright v kindle
  • copyright security on kindle

No related posts.

{ 2 comments… read them below or add one }

jose-kindle3gwifi September 2, 2010 at 12:45 am

The buttons have been redesigned and relocating the previous and next buttons on both sides is good for righties and lefties The 3G is absolutely worth it. I don’t see anything for library books. That’s the feature everyone wants. Amazon should stop being shady not allowing EPub.

chris-kindle3gwifi September 2, 2010 at 4:25 pm

I’m still not sold on these e-book readers. The best books are real books. See I love to read the real ones but the cost of an e-book, probably a Kindle 3g wifi, is too not easy to resist. I read sometimes read when my husband is asleep. Not sure how many are backlit. Thanks for showing us these issues.

Leave a Comment

{ 1 trackback }

Previous post:

Next post: