Internet Publishing Can Pay Off
An anonymous reader writes "Leander Kahney of Wired News has an article (Net Publishing Made Profitable) about how the publishers of the free, online newsletter TidBITS have hit the jackpot with their highly focused Take Control ebook series (nicely formatted PDFs that are easy to read on screen or print). Authors earn 50% royalties, and the books cost $5 or $10, with free updates. All the books out right now are about Mac topics, but maybe they'll branch out in the future."
Baen has done it, and it worked great. Cory Doctorow has done it (I think his publisher is Tor), and it worked great. I've done it, and it worked great.
Find free books.
I'm the author of two of these books and have been using a Mac since 1985. I'm not going to pump up my own effort, but I can tell you how much of these books arise specifically from the fact that we, as authors and experienced Mac users, couldn't find complete and/or accurate answers to the questions that the books address, nor could we find the comprehensive start to finish advice that we needed.
Our books aren't "here's menu A, here's menu B." The whole point is that they're not exhaustive, but they focus in on specific details. The books try to solve problems and to do it in finite space.
It would also be another thing if you could spend a few minutes and find the answer on Google for everything in the 50 to 100 pages in the books. But you can't. It might take you a few minutes per page to find what's in the book. So if you spent, say, 2 to 4 hours, you might save $5 to $10 -- if you could find the information.
My first book on file sharing took me about 60 hours to write on top of my experience with Unix (1994 to present), Linux (1997 to present), and Mac OS X (10.0.0 to present). The AirPort book that I just released a few weeks ago took less time in the first edition, but we commit to releasing updates with new and updated material--version 1.0 was about 90 pages; 1.1 (a free update for 1.0 book buyers) will be about 160.
Another interesting interaction with the ebooks is that we hear from readers and can practically immediately make changes. People who bought my AirPort books first version gave me great feedback. I incorporated almost all of it into new information for the 1.1 release, which all of these readers will get for free. I love that.
I hope this clears up a few of the issues. Almost all of the writers involved to date are freelancers, and it's really quite difficult to make a good living writing about using technology, which, I hope, helps other people. These ebooks make it financially possible for me to write books on topics that people are asking us for but that aren't available in a few minutes of Google searching, and that aren't cost effective for a print book, which has to sell 5,000 to 10,000 copies (depending on size) to be even a reasonable success.
Imagine, for instance, a 50-page book on regular expression pattern matching for Mac OS X users. It's a possibility, and would be highly useful. But you can't write a print book like that. (Although O'Reilly has a more generalized book on the topic in print!)
Freelance tech journalist for the Economist, MIT Technology Review, Macworld, and others
I've been running my own online publishing service since December 2002. Weekly e-mail chess training newsletters in html/pdf. It's been quite successful as a one-man show. I don't use any DRM and encourage subscribers to share with friends. Going on the "pixels are cheap" formula I priced things very low. Apart from the "lemonade game" aspect of having more subscribers with a lower price vs fewer paying more, having more happy subscribers works on word of mouth.
/. crowd.
I could put bugs in the html and DRM into the PDF to see who is forwarding the newsletters to a dozen friends, but all you do is force people to take more care with their piracy. Since you'll never stop a determined pirate, why hassle everyone else? I'm sure this is "Doh!" material for the
I wrote the file sharing book, so I'll respond to you directly. It's not an electronic pamphlet. It's over 100 pages of focused advice. It's $10 because that was the optimum price that allows us to sell a relatively small number of books (about 2,000 so far) while compensating me in a reasonable manner for the time it took to write it, and the ongoing time I spend in answering email and revising it. It's actually worked out perfectly.
The book isn't (as I noted in another Slashdot post), select this menu item, click start, next task. I explain how to modify Apache to set up WebDAV under Mac OS X. I have details on creating custom Samba shares. I explain the bugs in Apple's implementation of lukemftpd which prevents proper use of chroot and how to get around it.
Low-level topics these ain't if you've seen the book. This thread on Slashdot has given us a lot of good feedback, but the critique is all coming from people who are IMAGINING what's in the books, not actually looking at the site, downloading the free samples, and then responding.
The economics of publishing are really weird, too. The DVD Studio Pro book you bought for $20 gives a royalty of between $1.50 and $3 to the author or authors per copy sold. The book has to sell over 10,000 copies at that price and size to really make any money for the publisher. If the author worked alone, they might wind up making between $30 and $50 an hour for their time. Not bad at all, but not a massive return.
We're producing these niche -- not low-level -- books for intermediate users who need specific information and don't want to buy $40 and $50 exhaustive books. The exhaustive books are great for general reference, but my file sharing book has details that I was unable to find in any of the giant Panther books: they perversely don't have the space to cover every scenario in each topic because they have to cover EVERY topic.
Freelance tech journalist for the Economist, MIT Technology Review, Macworld, and others