I was fearful and uncertain about webM when I first read the analysis of the spec from "Diary of a x264 developer". Well before a lot of this fighting began. The fear, uncertainty and doubt comes from no real answer about anything. If this generates an answer by having Google fight whatever patent claims turn up in court (or a pool created for webM), we might actually get a hard answer in some form of official legal document. It may not be the answer we all want, but I have a hard time putting all my faith in a spec that was originally created in the dark, bought, opened, having the owner not submit it for standardization and basically tell you that you're on your own if you decide to use it and get sued.
I'm sure MPEG-LA wants it's money by creating a pool for webM, but I see this as maybe removing the FUD by forcing Google to defend webM and hopefully knock down any patent claims submitted.
I understand what you're saying. I read your reply after I had already posted. But Honestly iBooks is doing it wrong anyway.. It seems like it was put in as a hack, because it changes the systems brightness permanently whereas instapaper and kindle seem to be based on a percentage of the current system brightness. Which would make sense if it's a layer that they're changing the transparency of. I don't, however, think this is malicious in its intent, though it is a bit unfair. Same with the lock screen stuff. It is probably safe to say that this is something Apple will open to developers eventually... after they're done playing.
Apple should just flag apps that use private API's and call them out for it when the user upgrades the OS in an alert dialogue-like fashion when they launch the app (or on the applications iTunes page). "This app is using private API's and may not function properly with your current firmware." Instead of rejection. But it's probably easier to reject than to publish a "purchase at your own risk" disclaimer. All that's going to do is get a lot of people to not purchase your application.
The AppStore acceptance and rejection policys, though, should get fully investigated. I would like to get into iOS development, but trusting my livelihood on such a seemingly fickle process makes me really nervous.
I'm sure MPEG-LA wants it's money by creating a pool for webM, but I see this as maybe removing the FUD by forcing Google to defend webM and hopefully knock down any patent claims submitted.