Author Encourages Users to Pirate His Book
mariushm writes "Peter Cooper, the author of Beginning Ruby, breaks down how he gets paid for the book, including the advance and royalties, giving a nice clean explanation of how authors get paid for their books. He also describes the negotiations over the second edition of the book, in which he begged his publisher, Apress, to offer the ebook version for free, believing (strongly) that it would promote sales of the paper book. He even notes that the original version's ebook barely had noteworthy sales, so it seemed reasonable to offer up the ebook for free to drive more attention. No dice. Even though Apress has done that with other similar titles, it wouldn't agree. As he retains the copyright for the actual text, he encourages people to buy the book and create an online version of it without covers, contents table and indexes, promising not to enforce his copyright over the new work."
I have dealt quite a bit with copyright law when creating FairSoftware's virtual company license. I'm afraid the author is incorrect when he says that he retains copyright, therefore he can authorize people to download his book for free. He most likely granted the publisher an exclusive license. The whole point of the word exclusive is to say that although you are the author, you can't give the text to anyone else anymore, once you signed the book deal.
That being said, this is a great blog post for everyone who ever wondered how tech book deals work. He is making about $2 per sale of a $40 book! So there's a great debate about whether to go with an editor which will take a much lower cut, but will also not be so good at promoting the book. At least someone is making money from publishing content related to open source technology :-)
There are even links on Twitter to torrents like this. I am happy for you to pirate my book, but I’m NOT A LAWYER, and I can’t guarantee what Apress would do about it – so you’d be doing it off your own back! So, uhm, don’t pirate it?
So he's covered his own ass and recognized that Apress will most likely not see things his way. Now, to do what the summary suggests is confusing to me. I don't know his contract with Apress but I must question why, if he is so upset with Apress, he isn't just releasing an HTML version of his work online. Surely he must have the source documents he wrote to write the book, correct? Then why doesn't he simply make his own HTML plain text version and host it.
The answer is painfully simple. He's reached an agreement with Apress for digital distribution rights making them the only possible channel for distribution. I wouldn't be surprised if that was a default contract for them. Regardless, downloading the Apress version on RapidShare is copyright violation with Apress, regardless of what the author says. There's no question of that.
If I've misjudged Peter Cooper's character, I truly am sorry but he is either willfully or through ignorance putting you at risk with these suggestions. Do not follow through.
My work here is dung.
"All the traffic to the site is going to somewhere you can donate to a good cause and earn some actual karma."
Uh, yeah... and so now those of us who read the nonsense comments and thought "I'd like to see for myself what he really said" can't actually get to your original blog post.
Well played, genius boy.
Can't speak for anyone else, of course, but as for me... when someone hides his original words I'm not inclined to trust his claim that they were misrepresented.
So, you are unhappy with Slashdot's summary and the resulting comments, but instead of emailing the "editors", or writing a post like this one, correcting the inaccuracies as you perceive them, you redirected your site to the American Cancer Society, sending them hits from people who have no intention of going there, thereby costing them wasted bandwidth, and risking slashdotting their servers? Do you think that your pique, or your new-father status justifies that? Maybe your lack of sleep explains it, but it is all in very poor taste, and reflects very poor judgment.