I believe you can simultaneously sell an e-book in the iBookstore and sell a non-Apple created e-book with the exact same content somewhere else. For example, a word document turned into an e-book on Amazon. Just don't try and sell your Apple created e-book on Amazon, that's all.
I can also speak fairly highly of the leanpub team's process. My wife and I are finding it less than perfect for our needs in producing a fiction book with both ebook and print-ready book needs, but appreciate the directness and promptness with which both Scott & Peter have been responding to us when we are raising issues with what we're seeing.
Better yet, their conversion is free with no commitment to sell your book on leanpub required. I'd happily pay for what they're providing for free because it's so damned easy.
In fact, you can even sell an iBook—just like the ones iBooks Author makes—as long as iBooks Author isn't the program you used to make it. The iBooks Author software will inevitably spawn FOSS clones, and other tools that already exist (a likely candidate is Adobe InDesign) will allow export to the same iBook format in new versions, without the same EULA qualification. You might even just author an iBook "by hand," just the way you're currently able to author eBooks—writing HTML and CSS yourself, and zipping the results. You'll be able to have your cake and eat it too, just so long as you avoid Apple's particular cake mix.
The program is for creating iBooks, not eBooks, to be sold through their iBookstore. I'm seeing these more as apps than something like .ePub files or .PDFs.
Unlike apps though, which require an developer license to load yourself, Author gives anyone the ability to run these books on your iPad. It also gives anyone the ability to distribute an iBook outside the iBookstore.
Since licensing every person who wanted to create an iBook would be a pain in the ass for Apple and a barrier to creation, this seems to be the next good option.
It prevents anyone from creating their own iBook marketplace (reasonable) and profiting off of a software that Apple is giving away for free, under the agreement that products of it are sold though their marketplace. No?
What if everything you made with the OS was similarly hindered? Launch an auto update that effectively bricks your device unless you agree to the new EULA, blah blah nightmare scenario here.
Less hyperbolically, it's like the first concrete step into killing the freedom to read. My biggest concern with iBooks is whether they have remote wipe and whether you can launch books sans DRM.
It's going to be awkward when the PATRIOTSOPA Act of 2022 remote deletes all of my chemistry textbooks because terrorists can learn about exothermic reactions or revises all of the biology textbooks because evolution has been deemed illegal.
You can play the slippery slope card all you want, and try to apply what we're seeing to all other applications, but I don't see anything to back it up.
Regarding remote wipe. I have no idea if that's in the iBookstore EULA, and haven't found a thing about it. My guess is like apps, you'll have to confirm and download the update yourself. In fact, when apps are taken off the app store, you still get to keep them, whereas Android apps have a kill switch. Have you seen anything that implies remote wipe capabilities?
That is exactly what the author complains about, you cannot distribute an iBook outside the store:
"if your Work is provided for a fee (including as part of any subscription-based product or service), you may only distribute the Work through Apple and such distribution is subject to the following limitations and conditions"
The reason to say this was to make the point that unlike apps where you don't have the ability to distribute them outside of the store, the EULA is in this case necessary to lock down the user experience to iPad and resulting profits of providing this to Apple.
Problem with that approach is that receivers of the iBook can distribute copies at will.
I suspect the answer is this: you're free to sell the e-book version for a fee and give away the iBooks version: this just makes the iPad a more attractive product and undercuts your own e-book sales. This is probably a stupid move on your part, but that's hardly Apple's problem.
But giving away the iBooks version _only to purchasers of the e-book version_ is equivalent to the iBooks version being a "feature" of the (non-free) e-book version, which is quite different than "giving away the iBooks version". This would also apply to giving away the iBooks version, but only to members of my fee-based "book club", subscribers to my fee-based newsletter, and so on. Otherwise, what stops textbook publishers from selling non-iBooks "teachers' editions" for $10,000, then giving away copies of the iBooks versions to students enrolled in courses taught by holders of teachers' editions, then passing the $10,000 cost on to students by way of "enrollment fees" or tuition hikes, offset by the fact that "textbooks are now free"?
If you want money, you gotta use us.
You own a car, but you're licensed and registered by the state. You can paint it whatever color you want, but can you make an exact duplicate of that car and sell it as your own? Nope. Can you sell it without transferring registration? Nope (at least, not without alternate state paperwork). You might "own" it, but you still can't do whatever you want.
You're licensed iBooks Author and you enter into an agreement. You create, retain copyright, and own the product, but you can't copy it and do as you please. You follow the licensing and only have certain rights when it comes to the .ibook file.
A comparison in my mind would be saying GarageBand creations can only be sold through the iTunes store. The difference I see is that iBooks Author is not outputting a simple media file, but a more complex experience filled with medias. As often the case with Apple, they want to lock that experience (& resulting profits) into the best device for it, the iPad.
hm, you may be right. I got it from the paraphrased part of the article (right after the bold EULA text) but now that I look at it, it wasn't actually stated explicitly in the contract anywhere.
I can understand them saying that wanting to use the Apple store means giving them the same 30% cut that they charge for in-app subscriptions, and demanding that you adjust your prices on all other platforms to remain competitive. That's hardball, to be sure, but it respects the integrity of ownership.
This, on the other hand, is the same pattern that gets people hauled in on anti-trust charges. They're not a monopoly (yet), but I have a hard time seeing how this extraordinary claim of ownership in the work of others is anything less than the type of platform-abuse the anti-trust law specifically bans.
Let's say I write a book called "My Awesome Comments from HackerNews, Unabridged" (MACFHU) using Microsoft Word.
And I send that to my publisher, retaining all rights to publish the book still.
Then I adapt MACFHU for iBooks using the iBook Author tool. Would I then be prohibited from selling my book in the iBookstore because it's already available in hardcover? If I published it first in iBookstore, would my publisher be prohibited from publishing it in hardcover?
Or does the iBooks EULA basically say: "This is a specialized tool that you should use to publish books on the iPad." You can certainly publish your content on other platforms as well, but you'll need to format it using other tools. Check out InDesign, for instance.
I need some clarification.
1) Apple hasn't made clear enough that by using "iBooks Author", the only distribution channel you can use is Apple (de facto in that you must pay them, regardless of how you distribute).
2) There is disagreement that this is a good direction at all.
Point #1 is the one made by the author of the submission. With regard to point #2, I feel that Apple should be free to do what they want with their platform. I also feel that people should be free to openly disagree with them.
Apple are providing authoring tools for their "iBooks 2" engine and are not out of line expecting a cut of the profits...
I think the ownership is about the output format, not the contents itself, so it could be better compared to InstallShield, for example. It is used to package and easily distribute/install your Windows programs.
If it was free but they'd requested similar conditions to those in the iBooks EULA (that you can only distribute it in their own channels, that they might reject your program if they don't like it, etc.), would you still consider them for distribution?
The author is not saying that apple does not deserve a cut. He is noting that it is questionable whether Apple should be allowed to restrict the distribution channel
In all honesty, given the iPad's share of the tablet market, making unrestricted, high-quality, cross-platform interactive content development tools available to iOS developers at no cost might provoke antitrust claims from the likes of Adobe. But Adobe isn't likely to sell expensive digital publishing software to authors of free books, and mainstream publishers are unlikely to commit to "iPad exclusive" titles to avoid a few thousand dollars in software licenses.
As hackers, we are debating these books as if they are software, but remember that they are products at the intersection of two industries, and publishers have had authors in restrictive and less-than-lucrative contracts for a long time.
I think the root cause is the anti-piracy war, going on ever since the dawn of the computer age. The endgame may be an angry backlash of anti-copyright extremism gaining mainstream support. We may see a day soon when the voters demand an end to all copyright. Who knows what the end result of that would be.
Anyway, I don't see how that applies to a pretty printer for books. A mere tool is only that. I don't see why it should restrict my ability to commercialize my product. If someone were to suggest that the producers of pens, paper or canvas should have a say in how artists are to sell their works people would just laugh at him.
I imagine only true AI could hold the copyright to something -- and even than, the laws may currently be limited to human creativity.
IANAL but I don't think they're saying that if you use iBooks Author to make your work available for iBooks and use amazon's tools to make your work available for Kindle that you'd owe Apple a cut of your Kindle revenue.
You can get the payment, thats easy, you only take cash, there an ATM round the corner. Distribution is easy too isn't it.
If someone is unhappy about it, you can handle the returns. Or, no, sorry, of course you don't do returns. This is YOUR intellectual property - once they've got it, they may have photocopied it, you don't want your work to go around for free, do you.
In all fairness, you really don't need this - your website is already drawing an enormous attention and everyone wants a cut of it....
So what Apple is doing is legal and has precedent. But it's stupid so I hope and expect that they will fix this.
In both cases, the platform vendor is giving away nice dev tools in order to get more content to sale on his platform.
(read Microsoft as "Microsoft, Sony and Nintendo")
You mean like this? Applies to both Xbox and WinPhone. Apple also gives away Xcode, but you can't make iOS apps outside of their dev program.
And of course, if transcribing bypasses the restriction, then simply converting the file to a different format must do the same, right?
So much for the 21st century progress and freedom to own what you create.
You're a writer, but don't have a good typewriter. Apple is willing to lend you one for free. The only issue is that if you then want to sell your book, you have to sell it through Apple's store. If you don't sell a single copy, Apple won't charge you for the use of the typewriter. If you sell a lot of copies, Apple gets a cut, both for the book being in their store (publicity) and the use of their typewriter. You're still allowed to use different typewriters, and you can even sell books written on a different typewriter in Apple's store, though they'll still take a cut.
Doesn't sound terribly unreasonable to me
The only part where i have a problem is the exclusivity. Apple may own the typewriter but you own the words that you write. I think Apple may have a ground to charge you for using their typewriter somehow, but restricting where you decide to publish your work goes far, very far.
In the end, it's a matter of being in agreement with the contract. I doubt anyone reasonable would accept such terms willingly - an author wants to spread their works as much as possible, and not limit them to a single marketplace.
Actually, asking for a cut could become a standard option for selling software where you would offer at customer's choice:
- commercial license, paid upfront;
- commercial license, paid by royalties.
That way, people who don't agree to the GPL, but still think your commercial license is too expensive compared to their expected earnings would have a further option: no gain, no pain.
As a side note, one of the reasons I prefer software which comes with standard licenses (GPL, BSD, etc.) is that I know what those licenses say, and I can click on "I agree" without worrying about the fine print. If the license text differs in some way from its template, authors are explicit about that.
The only reason it would be unenforceable is if the terms are unreasonable. Unreasonable is pretty specifically defined in the common law, and it doesn't just mean that you and I don't like it.
In this particular context you would probably have to prove that there is economic duress, which might be a valid argument if Apple owned a monopoly on all textbook producing software and electronic textbook sales - which as of right now, they don't.
So barring something else more monstrous lurking in the EULA I'm not convinced that anything can be done about it (in court).
But the article is about the authoring tool, and Apple was going to produce it. So they had two primary options to protect their interests:
* Write an EULA and trust the law
* Use DRM in all output or otherwise proprietary formats (and implicitly trust the law as a backup)
I'm not saying we should be thankful for the EULA's wording, but for people who hate DRM for practical reasons, this is probably the best realistic outcome.
If you hate DRM for ethical reasons and think that all content should be free, then be happy about a free tool and write content.
Only if you wish you could use Apple's tool to make money on another platform, well you are out of luck.
> And as always apple using its market advantage
That must be a very limited 'always' :) I don't see how they abused the iPod's market domination much. The iPad is the only other product where they have an advantage in numbers, but I am not sure if that extends to the iBookstore at all.
Oh well, I just discovered iBooks Author does use a proprietary format, not ePub. Then of course it is not as useful for authors of free content.
Give it to your wife/husband for free.
Wife sells it for whatever and however she wants. Apple have no comeback.
This includes everything that is "free for non-commercial use", such as, if I recall correctly, Blender (in the past), most of the Free Fonts out there, and a lot of free software.
Edit to add: This means everything under the CC BY-NC-SA 3.0 license. There is a huge amount of content distributed this way.
The iBooks Author Software is an Apple provided development tool specifically for the purpose of creating iBooks for the iBookstore.
You can give your books away free in the iBookstore, and you can also, as you note, output the results in a variety of formats not suitable for the iBookstore. Those are a nice bonus.
Sometimes I get the impression that people think that everything should be free, for any use, and that the people who create these free things should have no right (or that its "audacious" to exercise some right) over what terms on which they distribute these free tools they create. (Or maybe only the "right" to distribute them on terms you agree with.)
Apple is providing a free tool, and the restrictions that come with it are the cost. Either the value of that tool to me exceeds the cost, or it doesn't. (and the "glovebox" example is nonsense, the EULA is part of the Mac AppStore sales process, you could read t before downloading the app.)
It is the same way with the Free Software Foundation. If they made a tool called "ePub Author" and that tool-- especially if it included templates and copyrighted imagery and other work, as iBooks Author does-- required you to license any works created with the tool under the GPL, then I'd make the same evaluation- is that restriction a cost that exceeds the value of the tool or not?
If you don't like the EULA, feel free not to use iBooks Author and use whatever tool you like that's value proposition is one you prefer. To rail against Apple for providing this tool seems to imply that you feel they owe you something.
Very often today we've seen Apple offer all kinds of new and innovative things, and I've seen a content stream of comments along the lines of "these are bad because apple profits from them". Of course Apple profits. We all profit, though, because they changed the economics of the education situation. If you want something different, create it.
We're not entitled to demand people to produce things for our benefit in ways we dictate, at no possible benefit to themselves.
2. Imagine if this product had been released to ONLY support iBooks in a proprietary format. Apple released a tool last year called iAd producer. This produced ads but only for the iAd network. It is completely proprietary. Nobody complained.
Would those who think these terms are unreasonable have complained if Apple hadn't included the ability to output in a standard ePub format, and the ability to distribute derivative works for free?
Is it really the case that making this tool more restrictive by limiting its interoperability would have removed these complaints? If not, how can you complain about Apple producing a tool to support their proprietary book format? Is Apple required to make all software capable of supporting whatever you want to do with it ? Should Xcode be require to produce Android apps?
Though I do agree with what you are saying: people have a choice not to use these tools. However, the rules of this product are somewhat hidden -- to the point where you probably won't know your restrictions until you've already put in the work. And also Apple is leveraging their platform dominance in an uncompetitive and unfair manner and should be admonished for it.
Do people really start putting significant effort into projects without thinking about legal issues, distribution, etc.? (I don't consider downloading an app and creating a two page test book as 'significant effort')
I haven't spelled its license recently, but the native code compilers are intended to keep authors locked into Microsoft's ecosystem. Whether that is more or less artificially then this product, I would not know.
Having said that, I agree that this is part of a strategy that is designed to corner a market. Some people would phrase that as "good old capitalism at work", though. I agree with them, except for that "good" adjective.
There is no artificial lock in. They are providing a tool to produce content for their distribution system. That's its point.
The comparison to general purpose tools isn't relevant. Consider if this tool, like iAd Producer, had no ability to export in a format outside of Apple's proprietary one. Would you still be upset?
>And also Apple is leveraging their platform dominance in an uncompetitive and unfair manner and should be admonished for it.
What platform dominance is that? The same people who complain about Apple doing anything that benefits them, seem to constantly tell us that the Kindle is the dominant e-reader and that android is the dominant mobile OS.
How is providing new features for electronic books "uncompetitive and unfair"? How is providing a tool that lets you author books that use these new features "uncompetitive and unfair"?
As for competitiveness, this is the very definition of competition. They provided something better, and also provided a tool that lets people easily create content for this better solution. Isn't your real beef that this is competitive?
As for "unfair", it seems that you're the one who is being unfair. You are taking the position that they should provide you tools for free to do what you want in any way you want. You seem to presume an obligation on their part to comply with your arbitrary view that they should give you something for nothing, without restrictions.
I believe the original author's pain is around the paucity of good EPUB publishing tools, and to have one appear with these restrictions makes them sad. It would have been nice if Apple had said, "If you buy a commercial license to this software for $X we won't constrain your ability to sell the books produced." Then at least there would be a way to use to the tool to produce books that would be salable at both Apple and Amazon's shops.
Clearly Apple sees this as a way to build a library of 'exclusive' content in iBooks and mute the Kindle threat. For me at least that shows me just how threatening the Kindle Fire is to their model.
Hell, iBooks Author exports PDFs. PDFs are viewable by Kindle Fires. (And possibly other Kindles.) So iBooks Author already creates content viewable on competitors' platforms.
I'm also not certain the Fire is threatening to Apple. They make far more money off of the hardware than they do off content sold through their various digital media stores.
iBooks Author is not a reaction to the Kindle Fire. Apple has been working on this since before there were rumors that Amazon was going to introduce a tablet of their own.
Steve Jobs even told his biographer about it . Jobs passed away in October, a week after Amazon announced the Kindle Fire.
I don't read it that way at all. I think they want to be properly informed (fine print not counting as "properly"), because they intend to avoid any platform that does this entirely.
There are real issues with gpl code that makes other derived works also gpl and there are reasonable discussions to be had about it besides "the person who created it can do whatever he wants. End of story". Same thing applies here.
The problem is also that it's this kind of attitude that allowed Microsoft to illegally leverage its monopoly to pressure other markets, with the excuse that "Hey, you don't have to use Microsoft if you don't like their terms".
It’s still possible to be disgusted by this for purely moral reasons. Apple is pulling some vile bullshit here and they shouldn’t.
Are you saying that Apple should make this tool for free, give it away for free, and let it be used for any purpose, for free, and that to do otherwise is immoral? (you brought up being disgusted "for purely moral reasons")
How is giving software away for free to support an ecosystem you're building "vile bullshit" that "disgusts" you?
For all the other examples you give, society generally knows the implied contract. These terms are not part of the contract that society expects from a free tool used to compose documents, and you know it.
Also worth mentioning: the economics of K–12 textbook publishing are very different than mass-market publishing: essentially 100% of sales are volume purchases by educational institutions who are already accustomed to distributing materials to students.
This is Apple's proposed alternative to publishers bundling interactive content with expensive textbooks (probably "free" if available on the App Store), and the value proposition is wide exposure, lower infrastructure costs, and no used textbook market to undercut profits in exchange for "a la carte" distribution of individual "unbundled" books and a unit price cap.
In other words, it really is an attempt to apply much of the "iTunes business model" to textbook publishing, and it'll be quite interesting to see how it works out.
And the iTunes business model was never about exclusivity. You can buy most of the music on iTunes elsewhere. (There is some exclusive content, obviously, but it is the exception, not the rule.) And, most importantly, the deals negotiated to get music on iTunes are done the old fashioned way: as a mutual, signed agreement between Apple and the labels in question.
When Apple praises their education initiatives and then turns around and puts such restrictions on their authoring tool then yes, that’s some vile bullshit. They are not in it for the eduction, they are in it for themselves.
They don’t have to give the tool aways for free, I would be perfectly happy with Apple selling it. But putting such a restriction on it? I’m not ok with that.
These are not mutually exclusive. They're in it for the education, and they are in it for themselves.
You're in it for yourself too. I think that's the problem that trips people up. They want companies to act a certain way because it benefits them. But when the companies do something that benefits the company, somehow they think that's wrong.
I'd love it if my favorite gave me free food all the time. If my restaurant offered me free food if I'd put a gaudy sign on my car advertising the restaurant that's a choice I could make.
If I didn't like the sign and didn't take their offer, I wouldn't then say "well that's just wrong of them to offer me that!"
> I would be perfectly happy with Apple selling it.
I think when it comes to software, people are so used to getting things for free, that when they see something encumbered by a restriction they think that this is somehow immoral.
Its not, its just a different way of selling the software. Just like the restaurant, rather than selling me food for money, selling me food in exchange for advertising.
True, but there is something immoral about hidden fees.
Are you arguing that this is not a fee or that it's not hidden?
You can produce all the books you want and give them away for free, without paying Apple a fee of any kind, and the notice is prominently displayed right on the screen where you publish your document.
This is no different from the zillions of dual-licensed GPL projects out there that say (roughly) "You're free to use this code in projects that you yourself give away for free, but if you want to sell your application you have to buy a license from us".
Again, I don't like this myself, but let's not make it out to be worse than it is.
Yes, a notice is displayed after you've already put a lot of work in, that is exactly what makes it slimy. A conditional fee is still a fee.
> This is no different from the zillions of dual-licensed GPL projects out there that say (roughly) "You're free to use this code in projects that you yourself give away for free, but if you want to sell your application you have to buy a license from us".
This is nothing like that. GPL projects do not hide their terms. And developers are very aware that libraries have terms. It is typical. An exportable document format having terms is not typical.
The user will not anticipate these conditions. This is why I call it a bait-and-switch. A company that prides itself on putting UX first couldn't have done this on accident. Either the product passed through QA without UX concerns being raised, or the concerns were ignored.
It's a slimy, used car salesman approach. Apple is better than this.
The price of a product is not determined by the effort put into it but by the value it provides to the buyer.
That library -- per definition part of GCC -- had to be explicitly made exempt from gcc's GPL license: http://www.gnu.org/licenses/gcc-exception.html otherwise yes, all your compiled code would have to be distributed using GPL.
For a long while RMS blocked adding plugins to gcc because he though that would allow proprietary vendors to violate the spirit of GPL.
I'd expect other languages that compile to binary code to fare even worse here -- gcc is better at separating its helper library -- but I'm not sure what other compilers than gcc are GPL'ed.
Someone please correct me if I'm wrong. I'm not willing to wade into the sea of legalese that is the GPLv3 right now just to verify this.
It would be impractical for the GPL to determine what counts as DRM and what does not; so they merely require "free modification of the Software".
Thus an iBook produced with the app is a derivative work that includes within it Apple copyrighted code.
Apple's ability to restrict the use of such derivative works is the very same ability the GPL relies on.
Don't attribute to others derogatory actions as an argument technique.
>This is where your analogy breaks down because this is explicitly not the case.
The existence of software that does not fit my analogy does not change the fact that there are many situations where the analogy still holds. In fact, the GPL itself is an example of the analogy holding- the GPL prohibits certain kinds of commercial use of creations derived by the thing protected by GPL, just as the Author app does.
That said, a person would be foolish to write the entire book using this. Write your text and create your graphics in your editors of choice, import them into this tool to create a nice layout for the iBookstore, then import them into another tool to create a nice layout for Kindle or whatever. You might have to do that anyway -- I've yet to see a tool that will generate a nicely-formatted ebook in both MOBI (Kindle) and ePub formats. Conversion tools like Calibre work if all you care about is reading the text, but the output often looks like ass if the original eBook used anything other than the most basic formatting (that said, a lot of commercially-produced eBooks look like ass anyway, so maybe that's not such a big deal).
For an anology, consider MS Word. When I create a document using MS Word and save it in one of Words native formats, this file includes all sorts of information generated by MS code and includes MS specific formatting information. That does not, in any traditional meaning of the word, mean that my essay is a derivative work of MS Word.
These files don't just contain "formatting information". They contain actual executable code created by Apple. Apple's claim lies on the distribution of their code, not your content per se. They can put any restrictions on the distribution of their code that they want, whether we like it or not (and I don't particularly like it myself). They're not claiming ownership of your essay. They're claiming ownership over the code they wrote, which their system uses to display it. Not the same thing.
What you, and others, are claiming is that this type of license has no legal effect. That's clearly wrong.
Let's not confuse the two issues of whether it's a good idea for Apple to do this (it isn't) and whether they're legally allowed to do it (they clearly are).
But a derivative work of the base template (normal.dot?), yes. If the template was released as NC-SA, then the resulting document is NC-SA.
Whether I personally believe in my gut if it is right that these books be deemed derivatives is a separate issue.. ;)
This is not an uncommon thing to see. IIRC, the gcc compilers have an explicit exception clause that says that programs compiled with gcc (e.g., the output) are not affected by the GNU GPL. A compiler usually does more than just transforms code from a higher-level language to a lower-level language. It can reorganize the code (-O2, -O3, -O4); it can inject standard or custom implementations of common behaviours that the user didn't explicitly write.
From a very real and very strict standpoint, a compiler/code generator does create a derivative work (and there's at least one code generator I've used in the past few years that holds this to be true explicitly; gSOAP) that is a combination of your copyrighted code and the code by the compiler writer (and possibly others involved).
There is no ground for any of this.
Comparing the history of "Apple-branded Mac software for which Apple does not charge users license fees" with the history of the "free for non-commercial use" software projects of the world is...a stretch.
Xcode is free. GarageBand has been included free on any semi-recently purchased Mac. iWeb who knows; Keynote, Pages, and Numbers are very low cost (and FWIW they each probably share code with iBooks Author).
Imagine for a moment that the next update to Xcode or GarageBand included EULA language similar to what the OP is complaining about. Would you defend it on the grounds you cite above, or not? And if not, why not?
Are there any other free applications on the Mac App Store that contain similar license language? If a third-party developer had a free application rejected from the Mac App Store for including this type of license language in the EULA, would you be surprised, or would you find the rejection consistent with the expectations that Apple has set for non-expert users on the platform?
If the "iBooks Author" application were something that had to be downloaded from inside an iBooks Developer Program portal, where you had to accept the license language as an explicit step to getting a portal account, I wouldn't care so much. But Apple literally held a press conference to tell the whole world "hey this shiny free shovel is going to enable happy rainbow pony time for the children, and everyone with a Mac and something to write for the children should download it right now and start digging."
>Very often today we've seen Apple offer all kinds of new and innovative things, and I've seen a content stream of comments along the lines of "these are bad because apple profits from them". Of course Apple profits. We all profit, though, because they changed the economics of the education situation. If you want something different, create it.
I totally agree with you on this point. And I would even agree that it's the most important point. In return, all I ask is that you join me in finding their EULA shenanigans slightly scummy in their bait-and-switchness.
The Xcode example is already a reality. If you produce an iOS app using Xcode, you have two choices: sell it for a price in the App Store and pay Apple a cut, or give it away.
I would not be at all surprised if the Xcode EULA contained language enforcing this now that you are no longer required to have an ADC account (free or otherwise) to download Xcode.
The greater point stands. If Apple had made iBooks Author only able to publish to the iBookstore, no one would have been surprised. It's their platform, and they do as they please. Don't like it, don't use it. I know a few publishers that are making this very judgement call right now: build our own web-based platform, or pay Apple's vig. Sure, they'd love to use Apple's tool for free. They'd also like to stop paying $1200 for Adobe's Creative Suite, but that's not happening either.
* The Xcode example isn't a reality. I can see my Mac application outside of the appstore without giving Apple a penny. I can sell my corporate iPhone / iPad application without giving Apple a penny (corporates can obtain management tools that allow them to load applications without using the appstore). It's true for a subset - consumer iOS apps.
* I've had Xcode prior to it's free availability in the appstore and have never had an ADC account - it was on the CDs with my MacBook.
On the first point, I was specifically referring to iOS apps, and you cannot "sell my corporate iPhone/iPad application" in the way you describe. Side-loading is only available to businesses with more than 500 employees, and as far as I understand, is only for internally developed applications.
Fair enough on the second, but it's tangential to the point. Apple constrains the distribution channels of iOS apps built using Xcode. This specific case is analogous to the iBooks Author tool restrictions.
We may be not entitled to demand people to produce things for our benefit, but we're certainly entitled to demand the freedom to do what we want with already produced things.
The only difference between those two example is temporal. I don't think that difference makes a difference.
Do you have the right to demand that people who have already produced some software, give it away for free and never be allowed to charge for it?
No one can say this tool must be used in this way so we make money. If they need to make money off the tool, they should be charging for it in some way.
The thing produced here is a derivative work that contains Apple created code and content.
Taking your words and changing the context produces this:
"if you produce a [some software], no matter how you produce it, [or who elses code you include with it.] you have the right to determine what [license agreement you use]."
See how that doesn't work?
Also, while your anology to the FSF is technically correct, I think it is safe to say that the FSF as currently governed would not do that. So, while your point is valid, it is a bit misleading to identify them by name.
BTW, Blender is pretty standard in this regard.
"Anything you create with Blender - whether it's graphics, movies, scripts, exported 3d files or the .blend files themselves - is your sole property, and can be licensed or sold under any conditions you prefer." 
But I did NOT downvote him/her on HN and I'm sad to see that his/her post has been downvoted. That's just wrong. If you don't agree say way, don't downvote.
I think part of the reaction is that people are used to paying for creative software. Imagine if Adobe had terms like this in Photoshop that required you to use their stock photo agency for any photos edited with photoshop. That would be outrageous and I would be right there with everyone saying it was wrong.
The difference is, Photoshop costs $600 or something (don't know or care, but they charge for the software) while iBooks Author is free.
What if iBooks Author had no other output modes-- just published iBooks to the iBookStore. And that's it. No PDF export, no epub. (Assuming in this example iBooks were more proprietary than they are- say like kindle's proprietary format is.)
Would people be upset about that? It would be a free tool for publishing to a proprietary formant for a specific store.
How could you complain about that? Apple's offering a tool specifically for their publishers. (I'm sure some tool exists like this for iTunes Album content. Another example of this is the iAd Producer software Apple makes which only works for iAds.)
If this product only working in a proprietary format would cause people to not complain--- because obviously the product was built to support the iBookStore-- then really the outrage is that you can use the product for other uses as well, Right?
So, Apple gives you the ability to produce ePubs and PDFs for free, if you want to. They add this feature, and now this product is somehow unreasonable?
Sorry, cek, if you aren't interested in debating this, that's fine. You didn't give reasons for why I was wrong, I just thought of this argument while responding to you. You don't have to engage on the topic further, no biggie, as I may not be responding at all to the reasons you think its wrong.
I think that's the point. You can't use it for other purposes. This is classic bait-and-switch. It has all of the appearances of a content-creation tool like people have used for decades, but it is not.
If you don't like the EULA, don't agree to it and use something else.