Slashdot Mirror


Nokia Urges Linux Developers To Be Cool With DRM

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.'"

34 of 536 comments (clear)

  1. Say what?!? by nahdude812 · · Score: 5, Insightful

    but we are not yet ready to play by the rules; but this needs to work the other way round too
    So you're not yet ready to play by our rules, but you want us to play by your rules so that you have an opportunity to take advantage of the work we produce and provide to you for free (beer/speech); when the only stipulation we have is that you provide it back for free?

    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.
    1. Re:Say what?!? by WiglyWorm · · Score: 4, Insightful

      I wish my moderator points didn't just expire. Hit the nail on the head.

    2. Re:Say what?!? by mdmkolbe · · Score: 5, Insightful

      If that is their plan, they must not realize the low value of QT (we have plenty of alternatives) compared to the high value of the no-DRM ideals in the F/OSS community. They really aren't in a bargaining position.

    3. Re:Say what?!? by qortra · · Score: 5, Insightful

      Absolutely, and given the choice, I would choose a forked community QT over compromising our values concerning DRM. However, it would be unfortunate to lose the support of a larger organization dedicated exclusively to improving QT. Do you remember the recent article on the the stalled XOrg development? People don't like doing low level, thankless, GUI stuff. They like making interfaces, not improving the speed of existing widgets. It would be difficult to get a sufficient number of people to work on the project reliably, IMHO.

    4. Re:Say what?!? by erudified · · Score: 5, Insightful

      "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,'

      I read this, and interpret it as this:

      "Jaaksi admitted that going 140mph in a 55mph zone 'goes against the public safety philosophy,' but said it was a necessary component of his fast-paced business lifestyle. 'Why do I need to do 140mph? I do,'

      I love this guy.

    5. Re:Say what?!? by 99BottlesOfBeerInMyF · · Score: 5, Insightful

      Do you remember the recent article on the the stalled XOrg development? People don't like doing low level, thankless, GUI stuff. They like making interfaces, not improving the speed of existing widgets.

      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.

      It would be difficult to get a sufficient number of people to work on the project reliably, IMHO.

      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.

    6. Re:Say what?!? by sgt+scrub · · Score: 4, Insightful

      It would be difficult to get a sufficient number of people to work on the project reliably
      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.

      --
      Having to work for a living is the root of all evil.
    7. Re:Say what?!? by clang_jangle · · Score: 4, Insightful

      I read it as a ransom note too, but I don't think the hostage is qt -- it's freedom to run our code on a phone, period. It isn't too hard to envision a time when hacking a device connected to a proprietary network becomes a criminal offense.

      --
      Caveat Utilitor
    8. Re:Say what?!? by uuxququex · · Score: 4, Insightful
      Now everybody else is considering going to PostgreSQL.

      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?

    9. Re:Say what?!? by MBGMorden · · Score: 4, Insightful

      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. That might be better in the long run. PostgreSQL in most people's opinions is a far better database for just about anything. As a former MySQL user, I've been attempting to switch over all my existing stuff from MySQL to PostegreSQL if the app supports it. So far, everything has been working nicely (MySQL on the other hand, has corrupted at least 1 database beyond repair for me before).

      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.
      --
      "People who think they know everything are very annoying to those of us who do."-Mark Twain
    10. Re:Say what?!? by Goaway · · Score: 4, Insightful

      "Clueless"? He is pretty much spot on. Clueless to try and fork in the first place, perhaps?

    11. Re:Say what?!? by qortra · · Score: 5, Insightful

      DRM and the GPL isn't incompatible is it? GPL 3 and DRM are relatively incompatible.

      I really don't understand what all the fuss about DRM in an open source world is. Then you don't understand the impetus for Free Software. Among the many and diverse goals of free software developers, one particularly prominent goal is to break down IP barriers that have previously obstructed use and development of software. In the case of GNU, the specific IP encumbered product that was being avoided was AT&T Unix.

      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?".
    12. Re:Say what?!? by 0xABADC0DA · · Score: 5, 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. Oh you have the right to purchase something that uses DRM or enter into an agreement with a company that uses DRM in their products. Also, the company has the right to reimplement every open source code they would have used in the product, and you have the right to pay the cost of that.

      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.
    13. Re:Say what?!? by mrchaotica · · Score: 4, Insightful

      I really don't understand what all the fuss about DRM in an open source world is.

      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.)

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  2. Here's an idea? Want DRM in your product? by base3 · · Score: 5, Insightful

    Write your own damn code!

    --
    One CPU cycle wasted on digital restrictions management is ONE TOO MANY.
    1. Re:Here's an idea? Want DRM in your product? by nahdude812 · · Score: 5, Insightful

      DRM is 100% Security Through Obscurity. They give you everything you need to produce an unencrypted version of something, and hope to high heaven that the only time it ever exists in unencrypted form is some place you don't think to look for it.

      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.

  3. Translation by dreamchaser · · Score: 5, Insightful

    "We want to ditch your rules but have you live by our rules. We know it's wrong and bad for consumers but too bad. We want to lock in our profits".

    Pretty typical attitude in the industry I'd say.

  4. Emotional? by Opportunist · · Score: 5, Insightful

    Huh? A corporation talking about emotion?

    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.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    1. Re:Emotional? by Opportunist · · Score: 4, Insightful

      The problem they are facing is that DRM and OSS don't mix easily. If at all. How do you want to enforce any kind of DRM when you open your source code?

      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.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  5. SIM locks?! by jez9999 · · Score: 5, Insightful

    Are you shitting me? IP rights are one thing (we don't expect people not to respect IP rights, we may disagree a bit on how extensive those rights should be), but SIM locks are an anticompetitive abomination, and this guy is a moron if he expects intelligent developers ever to like them. They're all about vendor lock-in, and removal of consumer choice. I bought my phone independently of a contract. It cost more but means I just put in whatever company's SIM I want and I switch providers that easily. Nokia, if you don't like that, fuck off. (It's a Nokia phone)

    1. Re:SIM locks?! by MoonBuggy · · Score: 4, Insightful

      I'm particularly surprised to hear this from Nokia, actually. It's been a few years since I was working with mobile phones, so maybe they've changed since then, but their SIM locks seemed like pretty much token efforts to appease the networks. Back then, at least, a lot of Motorola and Sony Ericsson phones were only unlockable with a full flash of the phone's OS while Nokias just needed a code that could be easily calculated from the phone's serial number. I always got the impression that Nokia wanted their phones to be unlocked - they don't make any money from the network contract anyway, so it was in their interests to have the handset itself as useful as possible to the customer.

  6. Re:Based on the quotes in the article header, by plover · · Score: 5, Insightful

    I RTFA, and it's actually an accurate summary of his speech. It really sounds like the guy honestly believes the crap he's spewing.

    --
    John
  7. I'm cool with DRM by Skapare · · Score: 4, 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.

    --
    now we need to go OSS in diesel cars
  8. Have cake, eat it too. by seanellis · · Score: 4, Insightful

    "As an industry, we plan to use open-source technologies, but we are not yet ready to play by the rules."

    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?

  9. Re:They need us more than we need them by Opportunist · · Score: 4, Insightful

    Educated? I'd say LARTed.

    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?

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  10. Two simple principles: by Rinisari · · Score: 5, Insightful

    If I don't control it, I don't own it.
    If I don't own it, I can't trust it.

  11. even open source cant make DRM work by RiotingPacifist · · Score: 4, Insightful

    1) encrypt something
    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.

    --
    IranAir Flight 655 never forget!
  12. Blah blah blah rahhh rahh by Idaho · · Score: 4, Insightful

    "These are touchy, emotional issues"

    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.

    --
    Every expression is true, for a given value of 'true'
  13. In North America, providers sell most phones by tepples · · Score: 4, Insightful

    not having SIM locks would be in Nokia's best interest Unless it means that no North American provider will buy phones in bulk from Nokia.
  14. Oh Dear: Nokia Does *Not* Get It by segedunum · · Score: 5, Insightful

    "We want to educate open-source developers. There are certain business rules [developers] need to obey, such as DRM, IPR [intellectual property rights], SIM locks and subsidised business models."
    Educate them of what? Lock-ins are totally and fundamentally incompatible with open source software, and the natural reaction is to free up or move on to something you can actually develop software freely for. The notion of open source software means that nothing can be kept secret. That's the direction that things head in, and I would have thought that Nokia would have been all for it as it helps them sell more phones.

    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.
    You either play by the rules or there is no dialogue, and it ultimately harms you as well. I've never seen a successful 'mixed source' software company.

    Don't make your own version. The original mistake we made was to take the code to our labs, change it and then release it at the last minute. The community had already gone in a different direction than [us], and no-one was pushing it other than [us].
    Tough luck. If people want things like ogg support then they'll go and get it. Forking is a fundamental freedom, and it will happen more often unless you play by the rules more.

    "a huge responsibility from a desktop and user interface point of view to see how we play our cards"
    Rrrrrrrrright. What does that mean?

    and expressed a keenness to see KDE and Gnome brought "closer".
    Do some Googling on the last ten years. They are divergent codebases, and while they share lots of libraries like X, I don't know what he means by 'closer'. It's as good as it gets.

    Jaaksi added that he believed Symbian, the proprietary operating system in which Nokia has a major share, would still "in years to come [be] the best platform on which to create smart phones".
    So we get to what the problem really is, and why he's being defensive about LiMo. As time moved on the odds are that the platform of choice will be Linux and an open source GUI because of the very advantages from the very freedoms and rules that he derides. Manufacturers can pick up the code, not have to worry about NDAs, IP and exorbitant fees, and get on with it. Qt will probably lead the way with Qtopia and GUI toolkits on Linux based phones. It's about cost cutting and economies of scale. Nokia will either join the wagon or fall off it, and being defensive with Symbian is a bad idea.
  15. KDE Free Qt Foundation by SgtChaireBourne · · Score: 4, Insightful

    Here it is: the KDE Free Qt Foundation.

    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.

    --
    Beta is broken and the link to classic doesn't work. Stop wasting our time or there won't be anybody left here.
  16. Qt is not the loss, Trolltech is... by hummassa · · Score: 4, Insightful

    (as a contributor). Qt is GPL'd, and a fork is available at all times. Lots of good, GPL'd Qt software can only work with the fork if Nokia chooses to close it up. The loss are the good brains at Trolltech.

    --
    It's better to be the foot on the boot than the face on the pavement. ~~ tkx Kadin2048
  17. There are a few more good parts too... by Timothy+Brownawell · · Score: 4, Insightful

    Open-source developers targeting the mobile space need to learn business rules including digital rights management, Nokia's software chief has claimed.

    "In this industry, we don't care about our customers. If you want to work with us, you'll have to respect that."

    Speaking at the Handsets World conference in Berlin on Tuesday, Dr Ari Jaaksi told delegates that the open-source community needed to be 'educated' in the way the mobile industry currently works, because the industry has not yet moved beyond old business models.

    "Our business models are very fragile. Please don't break them."

    Jaaksi, Nokia's vice president of software and head of the Finnish handset manufacturer's open-source operations, said: "We want to educate open-source developers. There are certain business rules [developers] need to obey, such as DRM, IPR [intellectual property rights], SIM locks and subsidised business models."

    "Our business is based on customer lock-in, rather than customer satisfaction. Don't interfere."

    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."

    "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."

    Nokia's primary play in the open-source sphere thus far has been Maemo, the Linux-based operating system that runs on its N800-series tablet devices. These devices are popular among developers in the Maemo developer community but, being something of a testbed, have not yet seen much traction in the mass market.

    Ok.

    In his speech, Jaaksi detailed some of the lessons Nokia had learned in its work with the Maemo developer community, primarily the need to avoid 'forking' code. He said: "Don't make your own version. The original mistake we made was to take the code to our labs, change it and then release it at the last minute. The community had already gone in a different direction than [us], and no-one was pushing it other than [us]. Everybody wants to make their own version and keep it too close to their chest but that leads to fragmentation."

    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.

    The manufacturer has one other significant investment in open source, however: the software maker Trolltech, Nokia's purchase of which finally went through in the last few days. Trolltech makes Qt, a graphical toolkit that is used in the KDE Linux desktop environment and in much commercial software and is an apparently non-participatory member in the LiMo Foundation.

    Ok.

    LiMo is an industry consortium that is creating a common middleware layer to help Linux-based software make it onto handsets from a variety of manufacturers. However, neither LiMo nor Maemo use Qt or KDE, opting instead for the GTK+ toolkit and a Gnome-based desktop environment. This has led to a level of industry speculation that Nokia may withdraw Trolltech from LiMo, to use it for other purposes. Nokia statedâ"when it announced it was to buy Trolltechâ"that the purchase was to help it move into the applications market.

    Some people think that Nokia wants to go play by itself.

    Speaking to silicon.com sister site ZDNet.co.uk after his presentation, Jaaksi said Nokia was "only now" able

  18. Re:I don't know where to begin... by indifferent+children · · Score: 4, Insightful
    More to the point DRM doesn't need to lock out fair use.

    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".

    --
    Censorship is telling a man he can't have a steak just because a baby can't chew it. --Mark Twain