Nokia Urges Linux Developers To Be Cool With DRM 536
superglaze writes in to note that according to Nokia's software chief, its plans for open source include getting developers to accept things like DRM, commercial IP rights, and SIM locks. "Jaaksi admitted that concepts like these 'go against the open-source philosophy,' but said they were necessary components of the current mobile industry. 'Why do we need closed vehicles? We do,' he said. 'Some of these things harm the industry but they're here [as things stand]. These are touchy, emotional issues, but this dialogue is very much needed. As an industry, we plan to use open-source technologies, but we are not yet ready to play by the rules; but this needs to work the other way round too.'"
Say what?!? (Score:5, Insightful)
I'm sorry, it sounds like you have your head firmly rooted somewhere dark and unnatural.
"These things suck and hurt both you and us, and we won't bend on that. But we want you to work for us for free anyway."
Holy cow man, listen to yourself. This is our playground and we give you an opportunity to play in it for free; in return we purchase the goods you produce as a result. You play by our rules or we take our playground and our purchasing power to someone who will.
Re:Say what?!? (Score:5, Insightful)
Re:Say what?!? (Score:5, Funny)
Re:Say what?!? (Score:5, Funny)
Re: (Score:3, Funny)
Re:Say what?!? (Score:5, Funny)
Re:Say what?!? (Score:5, Interesting)
"We have QT, and unless you give us DRM software in 6 months, you can kiss future GPL releases goodbye!"
Re:Say what?!? (Score:5, Informative)
Re:Say what?!? (Score:5, Insightful)
Re: (Score:3, Interesting)
I love KDE very much, and if Nokia starts to hold QT hostage, I'd very happily donate a large chunk of my free time to QT development. In fact, it would be just the opportunity I'm looking for to get started contributing to OSS.
So, your sentiment may be true overall, but there are probably a few woul
Re:Say what?!? (Score:5, Insightful)
Actually, I think most Linux developers don't really enjoy the bit they are working on. They do it because they are being paid by a company who needs that part improved. With X.org, for the most part, it was not a problem for what companies want to use it for (mostly as a server). As companies start to use Linux for more applications (to sell consumer laptops, for example) they will invest more in areas like improving X.org in ways that will facilitate those uses.
Nokia could get out of developing QT, but someone else would move into the niche and undercut the prices of their proprietary replacement. It is simply too hot of a business opportunity to be ignored right now. Maybe the companies dumping money into QT development would go down for a while without Nokia's support, or maybe they would go up because people see an opportunity to make money. Either way, Nokia trying to use it as leverage is not going to get them too far.
Re:Say what?!? (Score:4, Informative)
Re:Say what?!? (Score:5, Insightful)
See. That is the reason for my comment on the Xorg article to the fact of "if someone insists on something being in your code tell them to pay you or f'off". Projects shouldn't be a matter of "getting enough people together to produce something". FOSS projects should be love'm or leave'm.
QT isn't exactly the only game in town for foss_gui. If QT fell off the map the underlying technology that lets QT draw the pretty pictures will continue to work fine.
I'm right there with you as far as principles go. Which brings it back to "pay or f'off". If someone wants something from you that is in addition to what you were planning or had time to do they should pay you. If these guys want QT to have BSware in it then they should pay someone to write it then ask for hooks to implement it within QT. If they kill QT over it then it is the original developers that get screwed. And trust me, if you screw the original developers on a project you will already have your "enough people" to fork the project.
Re:Say what?!? (Score:5, Informative)
But software that is comparable to X is very scarce, which indicates that THAT kind of software just isn't "funny" to do.
If Nokia ever would try to play hardball, I think a community supported version of QT would do just fine - KDE developers would most likely just pick it up, and if noone really wanted to maintain QT, it would simply die and we'd all use GTK instead.
So - I really don't see the same problem as with X.org here.
Re:Say what?!? (Score:4, Insightful)
(which is not to say that there aren't any good projects, but the ones with crappy interfaces and lacking documentation are certainly in the majority...)
Re:Say what?!? (Score:4, Insightful)
This entire no DRM stand is basically saying that I can't have the option to purchase something or enter into some agreement with a company in a fair and free society. Actually, as long as the licenses are followed and a proper disclosure is don't so someone doesn't think they are buying something just to find out later that they got a right to use it in a certain way with a certain device, the open source community should be pretty agnostic about the DRM. There really is no reason to fear it and there certainly isn't a reason to promote Microsoft's agenda by forcing companies looking for DRM to deliver some product in some way to use their crap ware. DRM and the GPL isn't incompatible is it? Certainly not that I am aware of unless it is being used to thwart the GPL terms. As long as that isn't happening, where is the beef?
Re:Say what?!? (Score:5, Insightful)
Implementing DRM in free software is in direct violation of that goal. DRM is a paradigm that, once again, is designed to build obstructions to the development and use of software and media. Asking OSS developers to build DRM solutions is like asking OSS developers to make "Linux Genuine Advantage" software to prevent Apt from working when the system is not "authorized", or activation software to brick your computer if you change the video card one too many times. Why in the world would an OSS developer do such a stupid thing? There simply isn't any utility.
So in short, the following question is purposeless: "is DRM compatible with OSS?" The question you should be asking: "why would an OSS developer donate his time to make his and everybody else's life harder?".
Re:Say what?!? (Score:4, Funny)
Re:Say what?!? (Score:5, Interesting)
no, that's not the question should be asking. I don't think any sane mind OSS developer would put their time to write DRM applications.
HOWEVER, would a company like Nokia have a reason to write open source DRM applications? Absolutely.
That said, they'd have to provide the source code which would then make circumventing their DRM trivial. So the only way this could work is if they got governments (looking at you Canada) to go along with criminal offences with respect to software that breaks locking mechanisms. They seem to be having success in certain countries.
So it's not unthinkable for Nokia to have a linux based mobile OS, with an open source DRM package that they use for media content (which means it can ported and the media can remain fully compatible). The only thing protecting the open source DRM from being hacked as the laws against it (as above). If this became the norm, I'm pretty sure you would see other develops using the nokia package to allow other applications to access the media. Maybe a plugin for media players... Or maybe nokia would develop those too.
I must claim ignorance as to whether or not the GPL would legally prevent open source DRM from being implemented.
Re:Say what?!? (Score:5, Insightful)
The changes in GPLv3 to fight DRM are entirely about the free market: either DRM adds enough benefit that companies implement their own codes or it doesn't and they use open source codes. It's up to the market to decide whether open source or DRM can coexist or if one dies. As open source developers, we write code for free and give it away under some license. If licenses with anti-DRM in them out-compete the others like say BSD then that is the market deciding that collaboration and spirit is more valuable than DRM.
When companies complain 'how can we compete with andriod when most of the cost was donated free by open source developers?' they are just whining. If they can't figure out how to compete then they need to drop DRM or die in the market -- that is a free market in action.
Re:Say what?!? (Score:5, Interesting)
Now suppose you want to want to play that music on your open-source device - say a Linux-based mp3 player. Since open source software guarantees you the freedom to modify the source code, there is nothing to prevent you from modifying the operating system or other open source code on the device to circumvent whatever DRM measure the vendor put in place.
This situation is of great concern to the DRM-using vendor. They wish to enforce your agreement by technical means (rather than legal means), in part because it avoids them having to know whether you're breaking the agreement you made, and in part because it's a lot cheaper for them than suing you for copyright infringement or breach of contract in the event you violate your agreement.
Thus the vendors start playing tricks like building hardware that will only run software that the vendor themselves digitally signed. This includes the GPL operating system and other GPL software on the device. This allows them to enforce their DRM, but also prevents you from exercising your freedoms under the GPL to run your modified software, even when your modifications are unrelated to the DRM you agreed to.
The free software community views this tactic as an attack on the whole point of the GPL. The DRM-using vendors simply don't care about the collateral damage their attempts at technical enforcement of DRM impose. But the free software community cares a lot about those freedoms.
That is why GPLv3 has explicit provisions against this sort of practice - if vendors want to use technology to restrict your freedoms, they can write their own software to do it. If they want to use GPLed software, they need to honor its terms (and hopefully the spirit too). What they can't do is have it both ways.
So to summarize - open source software gives you the freedoms that DRM companies aren't willing to let you keep, and gives them cost savings they aren't willing to give up. So instead they try to circumvent the GPL, creating the current conflict.
Re:Say what?!? (Score:5, Insightful)
The entire point of Free Software is to allow you, the user, to have control over your device.* The entire point of DRM is to prevent you, the user, from having control over your device.
Do you see the problem yet?
(* Ensuring that you have both the source code to the software (what all versions of the GPL did) and the ability to install and run it (what the GPL3 does, which is why it was necessary) is merely the mechanism by which the Free Software Foundation attempts to accomplish this.)
Re:Say what?!? (Score:5, Informative)
Re:Say what?!? (Score:4, Funny)
Re:Say what?!? (Score:5, Insightful)
Re:Say what?!? (Score:5, Insightful)
Re:Say what?!? (Score:4, Insightful)
Qt is not the loss, Trolltech is... (Score:4, Insightful)
Re: (Score:3, Insightful)
I don't know where to begin... (Score:5, Informative)
Second, attempts at implementing DRM are a _terrible_ thing -- because they are just attempts to prevent honest people from exercising their fair use rights, and lock people on carriers, distributors, or platforms. Nothing else. Forget the 'piracy!' screams, it just translates to 'the consumer wants to buy a CD and listen to the same music on his iPod without paying another fee for it' or 'the consumer wants to watch the movie on this DVD... but after, he wants to lend it to a friend, that will watch it and we will not receive any money for it'.
Re:I don't know where to begin... (Score:5, Insightful)
Yeah, it pretty much does. Unless your DRM system is a full-blown AI (with all the knowledge of a competent lawyer (for your jurisdiction)), how is it going to judge whether the mashup video that you want to create, using someone's DRM-encumbered audio stream, is a copyright violation or fair use? Does it depend on whether you are going to view your mashup in your own home, or send it to friends? Does it matter if you intend a commercial use for your mashup? Even an IP lawyer can't necessarily tell you how a judge is going to rule on a license violation issue (or whether the license is valid, meaningful, unconcionable, etc)
With DRM, the answer to your request to access encumbered content can never be "maybe" or "sometimes"; it pretty much has to be "yes" or "no".
Re:Say what?!? (Score:5, Informative)
Re: (Score:3, Interesting)
Mostly because I'm curious.
Re:Say what?!? (Score:5, Informative)
I hadn't heard of it before, either. Now I'm wondering: what additional power does this agreement give them? Presumably everyone already has the right to fork Qt.
Re:Say what?!? (Score:4, Informative)
Under the agreement, if Trolltech (now Nokia) stop releasing GPL-licensed versions of the Qt library for a period of time, for any reason, the last GPL-licensed release is to be relicensed under a BSD-style license.
In other words, the last GPL-licensed release of Qt will become free for any use, including use in commercial, closed-source software.
With the current GPL / QPL / commercial licensing arrangement, any software developed with Qt either has to be free and open source, or you're required to pay for a commercial license. A fork based on the current Qt would still have that restriction.
KDE Free Qt Foundation (Score:5, Insightful)
Here it is: the KDE Free Qt Foundation [kde.org].
If Nokia screws up and stops releasing FOSS versions of Qt or otherwise messes with it, Qt's forcefully taken from them. The Foundation is there to ensure that Qt remains available. In a lot of ways, it would make more sense to do this now before Nokia starts using it as a hammer to pound DRM where it doesn't belong. Further, Nokia's competitors would be stupid to use it while Nokia controls it. Tools like Qt belong under an independent company or foundation. Jaaksi is just making that very clear.
What Jaaksi seems to be saying on behalf of his employer, Nokia, is that the company is unwilling to abide by the license (the GPL) under which their new business model is founded upon. That's not a way to appear clever. Though it's good of them to put the cards on the table so early after acquisition, it's still rather shameful of Nokia to try to bullshit us like that. Probably time to check the resume's of Nokia execs and dismiss any moles from Redmond.
I'm not planning on giving up on Qt anytime soon, but I do resent the increased level of alertness required by these probes.
Re:Say what?!? (Score:5, Insightful)
Re:Say what?!? (Score:4, Insightful)
Project Mayo used this model...
MySQL used this model...
QT used this model...
And here we are.
MySQL, QT and DivX networks are *NO* better than Nokia. I don't care if MySQL never went commercial, it was much better as LGPL. Now everybody else is considering going to PostgreSQL.
Compare with wxWidgets. It may not be as popular in the Linux area, but a lot of Windows developers use it.
Re:Say what?!? (Score:4, Insightful)
Which is a better outcome than one could have hoped for. Postgresql is so unbelievably more stable and robust it isn't even funny anymore. MySQL might have been OK for read-only web backends, but let's not pretend it is a real RDBMS.
Postgresql, however, is technologically better and has a better license. What's not to love?
Re:Say what?!? (Score:5, Insightful)
Divx networks? We made Xvid.
If QT goes that route then we do have wxWidgets as you mentioned (which is a toolkit that I REALLY like - you mentioned Linux and Windows but the code also ports over to MacOS as well), or the obvious choice of GTK.
We will suh-vive.
Re:Say what?!? (Score:5, Funny)
Re:Say what?!? (Score:5, Informative)
Except people did consider this possibility and Trolltech signed an agreement specifically covering what would happen if they stopped releasing improvements to QT, specifically including cases where they had been acquired by another company. Basically they're bound to release it under the BSD license at that point, so we have a start for a fork just as good as what you mention.
Re:Say what?!? (Score:5, Interesting)
Hopefully at some point soon OpenMoko [openmoko.com] will become good enough for normal phone usage. Now there's a company that, from the very beginning, has wanted to play by our rules.
Want to get the linux community's support? Asus did it, even though I'm not entirely sure they realized it when they began doing so. By releasing a machine that's linux friendly and not locked down, you're sure to get a community surrounding you that will help even improve the usefulness of your product.
Re:Say what?!? (Score:5, Funny)
Re:Say what?!? (Score:4, Interesting)
I doubt opensource developers need any 'education' from Nokia; most understand those 'business rules'. And reject them. Nokia on the other hand, have been fairly consistently in favour of proprietary approaches, from support for software patents to DRM, etc.
The phone industry and its 'business rules' has brought us things like short text messages with profit margins in the range of thousands of percent of the cost, 'ringtones', drm'ed throwaway music, etc. I understand exactly how it works, as does anyone who hasn't had a rectal anesthetic for the last decade.
Over the longer term, open handsets stand to revolutionize portable computing. Unless the company changes philosophy at some fundamental level, I doubt Nokia will be part of that.
Re:Say what?!? (Score:5, Insightful)
I read this, and interpret it as this:
I love this guy.
There are a few more good parts too... (Score:5, Insightful)
"In this industry, we don't care about our customers. If you want to work with us, you'll have to respect that."
"Our business models are very fragile. Please don't break them."
"Our business is based on customer lock-in, rather than customer satisfaction. Don't interfere."
"We accept that we have problems, and that if we followed your rules we wouldn't have these problems. But instead, we want you to follow our rules and enjoy our problems with us."
Ok.
A common fear about BSD-style licenses is that people will make closed forks. If the project is active, this fear is very likely overblown.
Ok.
Some people think that Nokia wants to go play by itself.
Here's an idea? Want DRM in your product? (Score:5, Insightful)
Re:Here's an idea? Want DRM in your product? (Score:5, Funny)
Re:Here's an idea? Want DRM in your product? (Score:5, Interesting)
Re:Here's an idea? Want DRM in your product? (Score:5, Interesting)
Re:Here's an idea? Want DRM in your product? (Score:5, Insightful)
An open source DRM module couldn't possibly work. Well, it could, but it would be very easily crackable - instead of sending the unencrypted stream to the screen and speakers, send it instead to ff4mpeg or to a disk and have it re-encoded.
Every major DRM scheme has been broken to date, and that's without having the source code available. Having the source means you just redirect the output to some place you can capture it, and you're done.
Re: (Score:3, Informative)
Re:Here's an idea? Want DRM in your product? (Score:5, Interesting)
Yeah, but no:
mplayer -vo mpegpes:grab.mpg YourDRMfile.wmv
So, your DRM decoding module should set a flag in mplayer that forbids file-output. So I modify mpegpes module to ignore that flag, or for mplayer to lie to the DRM module about which output module is loaded. Hmm, so you require the mplayer binary to be signed by someone you trust, probably Microsoft or RedHat, and they'll charge $6000 pr release, even if it's a trivial but critical bugfix.
OK, I don't wanna do that, so I plug in a kernel-module that will always open
Then I get myself one of these videocards with a FPGA on it, and program that to dump the video-stream back into the memory, so I can copy it to disk - so you want your cryptographic chain of trust to include the videocard, and I put my FPGA in the other end of the DVI cable, and rip from there. So you demand access to a chip in the monitor, also.
So, no, you can't put a DRM module (that's worth anything, at least) in anything opensource, without making the entire system wall-to-wall closed (AND broken, too). Microsoft, whose customers couldn't care less about closed, tries to do this, and fails. ("What, I can't put my legitimately purchased Plays for Sure! file on my fucking iPod?")
Translation (Score:5, Insightful)
Pretty typical attitude in the industry I'd say.
Re:Translation (Score:4, Insightful)
Its unfortunately typical of a lot of bosses, regardless of the industry. Many bosses will arragantly use others, but don't want to give anything back (for fear of giving others a helping hand, as they may well end up being a competitor. So in their mind, its better to keep others down. They take, but don't give back. Its why they don't like open source, (when they have to compete with it), as its a threat to their way of treating others, as much as a threat to their products).
From the summary, "Why do we need closed vehicles? We do"
Yeah they do, as they want to control whats on their products, so they can charge whatever they like for them and if we don't like it, tough, as we will not get a choice, as they will prevent us having a choice, as they control whats on their products.
Based on the quotes in the article header, (Score:4, Informative)
Re:Based on the quotes in the article header, (Score:5, Insightful)
Re: (Score:3, Insightful)
this sounds rather like a declaration of war.
Interesting you say that. My thoughts were more along the lines of Open Source is to the Native Americans as Nokia is to the U.S. Government. That is to say there's many Open Source organizations and no single collective leader over all of them, making it very difficult to negotiate a, to resume the metaphor, peace treaty.
The fortunate thing is that I don't believe there is anything to be the proverbial bison that can be killed off to, in turn, wipe out Open Source.
They need us more than we need them (Score:5, Funny)
Re:They need us more than we need them (Score:5, Insightful)
Can you imagine what a cell could become if it is "OSS friendly"? Yes, you will most likely not lock your customers into having to use it, but here's a really novel, radical and completely unthinkable idea: They just might want to use your product because it caters to their needs.
I know it is so last century, but how about making a product again that the customer wants to buy instead of trying to force him to buy it with vendor lock-in snares?
Emotional? (Score:5, Insightful)
It's about money. It's about vendor lock-in, it's about customer control and about avoiding competition.
They want cheap/free (the beer kind) software, but under their sole control, without allowing the user of the software to apply it to their needs. Sorry, OSS doesn't swing that way.
Re: (Score:3, Informative)
Re:Emotional? (Score:5, Insightful)
My guess is that he fell for the fallacy of considering the "free" in OSS as "doesn't cost anything". OSS can actually cost something. Nowhere does it say you can't ask for money to write it. The "free" part means that it is released openly. And that's something he appearantly simply doesn't get.
Re: (Score:3, Interesting)
Re:Emotional? (Score:5, Funny)
It's about money...
You dont think corporates get emotional about money ?
Re: (Score:3, Funny)
In other news... (Score:5, Funny)
Re:In other news... (Score:5, Funny)
SIM locks?! (Score:5, Insightful)
Comment removed (Score:5, Insightful)
Re: (Score:3, Insightful)
In North America, providers sell most phones (Score:5, Insightful)
That's some great logic there... (Score:5, Funny)
I'm sure that will do wonders to convince all of the second-grade OSS programmers to help you out.
Me, I'm not interested. Because you're a doody-head, because you are.
Re: (Score:3, Funny)
RE (Score:5, Funny)
There is *no* cool way you can word it.
I'm cool with DRM (Score:5, Insightful)
... as long as it doesn't interfere with my rights to reprogram anything using any free/libre software and doesn't intefere with my fair use rights to use the content I pay for.
Re:I'm cool with DRM (Score:4, Interesting)
...as long as everyone completely ignores him and his orders.
-
Have cake, eat it too. (Score:5, Insightful)
Sounds like they are not yet in a position to use open-source technologies.
It would be interesting to see if turnabout is fair play. I'd love to have a free high-end smartphone, but that means taking up an expensive monthly airtime contract. Instead, I'll just declare that I am "not yet ready to play by the rules", take the benefit of the free handset now, and later on I'll sign up for a contract when I am ready to play by the rules.
OK?
Two simple principles: (Score:5, Insightful)
If I don't own it, I can't trust it.
Re:Two simple principles: (Score:4, Funny)
even open source cant make DRM work (Score:5, Insightful)
2) send encrypted data to their computer
3) send key to their computer
4) wait for somebody to take a memory dump
5) NO profit
Even if somebody was to make a binary blob to prevent memory dumps at kernel level, all you need is to run linux in a virtual machine (i hear its good at that) or use some rootkit.
Trusted Platform Module (Score:3, Informative)
actually, could just be closed source? kthx. (Score:4, Insightful)
Oh wait. They want DRM, which needs the software to be closed source. So I guess that's already what they are asking for.
And the "we need closed vehicles" bit? Worst car analogy ever. If you want to "close" your music, you encrypt it. What nokia wants are cars that locks from the outside when you get in, so you can't escape from them. Not sure that we really need those.
(*)fake quote. Keep the pony if you've already bought it.
The Answer (Score:3, Funny)
Funny guy (Score:4, Funny)
OK sure, we are 100% behind DRM. (Score:5, Funny)
Dont worry nokia, we got your back, it's there believe us. and it's Un-Crackable. We wouldn't lie to you.
I'm okay with DRM provisions in open-source (Score:5, Funny)
Blah blah blah rahhh rahh (Score:5, Insightful)
No, they are not. There are very rational and well-explained reasons for being against DRM, closed platforms, vendor lock-in and the like.
I'm not even going to repeat them here, because I assume them to be well-known (certainly to the Slashdot audience).
So that's some nice bullshitting and spin doctoring going on there, but no. Really, no.
Jaaksi's blog (Score:5, Informative)
Jaaksi, you seem to have misunderstood (Score:3, Insightful)
Oh Dear: Nokia Does *Not* Get It (Score:5, Insightful)
Hey Ari, (Score:4, Funny)
Stick it up your Jaaksi!
This is obviously a troll article... (Score:3, Interesting)
c'mon guys! really!
Inflammatory comments from a guy called Ari Jaaksi?
Ari Jaaksi - Hairy Jacksy (*)
Can't you even recognise a troll these days?
(*)Hairy Ass for non-Brits
Nokia says "we like open source" (Score:4, Insightful)
It's about the carriers (Score:4, Insightful)
Coming from someone that just bought a Nokia N810, that might sound biased, but... I think most posters here completely missed the point.
Nokia sells cellphones, and most of them are sold to carriers that want to use SIM locks and DRM to lock in customers to their plans and those stupid ringtones at $1.
Why do you think they use Linux almost only for "Internet Tablets"? No carriers would never sell a phone that's unlocked out of the box, and the vast majority of cellphones are bought with a plan, not unlocked.
Why do you guys think the iPhone is selling so well? Because it's unlocked? Because it's Open Source? And why do you guys think the iTunes music store grew so big at first? Because it was DRM free?
Nokia, RedHat, Sun are not making the rules. Business, cellphone carriers, and media companies are the ones lobbying governments, and until that changes there is no way Open Source software will grow unless we gradually change those rules.
Re:uh-oh (Score:5, Informative)
Re: (Score:3, Informative)
Yes we could fork it. But we also could fork it under the BSD license.
Actually the BSD license gives you more options, as you can fork something and turn it into a closed source application. The GPL does deny you that freedom to ensure that derived works stay Open source.
But in this case it doesn't make a difference:
The copyright owner (Trolltech) can always release new, closed-source versions. Unless they include other pe
Re:uh-oh (Score:4, Informative)
Re: (Score:3, Insightful)
Carriers? You mean those companies who don't want to allow consumers the freedom of choice? The companies that want to prevent you from playing any music you have legally obtained from somewhere else (whether it was paid for, or given away for free) and want to force us to buy everything from them?