Slashdot Mirror


VLC For iOS Returns On July 19, Rewritten and Fully Open-Sourced

An anonymous reader writes "VideoLAN revealed some very exciting news today: VLC for iOS will be back in Apple's App Store by tomorrow (July 19). The company tells TNW the app will be available for free worldwide, requires iOS 5.1 or later, as well supports the iPhone, iPad, and iPod touch. As you can expect, VLC for iOS version 2.0 will be open-source. This time, however, its code will be available online (also by tomorrow), bi-licensed under both the Mozilla Public License Version 2 as well as the GNU General Public License Version 2 or later."

142 of 203 comments (clear)

  1. 3 2 1 Takedown by kthreadd · · Score: 4, Interesting

    I don't understand how they think this will work. LibVLC is LGPL, and unless they got consent from _every_ VLC contributor or the terms and conditions changed dramatically the last couple of months they can't distribute it on the iOS App Store. Sorry, but you picked the wrong license if that was something you wanted to do.

    1. Re:3 2 1 Takedown by negRo_slim · · Score: 1

      Huh, I was curious what the initial issue was. Was it licensing? Because I thought it was due to duplicate functionality in iOS.

      --
      On the Oregon Cost born and raised, On the beach is where I spent most of my days
    2. Re:3 2 1 Takedown by Goaway · · Score: 1

      One of the VLC devs requested to have it removed because of licensing.

    3. Re:3 2 1 Takedown by DigitAl56K · · Score: 1

      This is probably where the "rewritten" part comes in. I would assume they either got consent or rewrote the parts that they didn't have consent for.

    4. Re:3 2 1 Takedown by kthreadd · · Score: 2

      The UI layer is MPL, but the actual guts of the app is libVLC which is not rewritten and licensed under LGPL. So, unless they rewrote that and I missed it I don't see how they can be in the clear.

    5. Re:3 2 1 Takedown by xeio87 · · Score: 2

      It was one of the VLC developers that complained about how the GPL and iOS TOS were incompatible and ordered it to be taken down.

      Basically, sour grapes.

    6. Re:3 2 1 Takedown by kthreadd · · Score: 3, Insightful

      Either that, or Apple could stop abusing its users.

    7. Re:3 2 1 Takedown by Kjella · · Score: 1

      Well yes the iOS front-end perhaps, but unless they also rewrote the whole decoding backend that they have to link to that part will still be under the LGPL.

      --
      Live today, because you never know what tomorrow brings
    8. Re:3 2 1 Takedown by Mike+Buddha · · Score: 2

      Basically, sour grapes.

      Yeah, some people just get all uppity about what you do with the things they created :(

      --
      by Mike Buddha -- Someday the mountain might get him, but the law never will.
    9. Re:3 2 1 Takedown by gnasher719 · · Score: 2

      The UI layer is MPL, but the actual guts of the app is libVLC which is not rewritten and licensed under LGPL. So, unless they rewrote that and I missed it I don't see how they can be in the clear.

      They are in the clear as long as none of the copyright holders complains to Apple and demands that the app is removed. And once one of the copyright holders complains, it doesn't matter whether the app store is compatible with GPL or not, because Apple will remove it when asked to do so.

    10. Re:3 2 1 Takedown by BasilBrush · · Score: 1, Interesting

      It's not Apple doing the abusing. It's the GPL that is incompatible with the App Store. There's no Apple rule that stops GPL software appearing on the App Store.

      The only reason users of the iPhone haven't had VLC for all this time is the GPL and the decision by it's developers to remove it. It's not as a result of anything Apple has done.

      It's good to see an outbreak of common sense, and the use of a non-GPL license this time round.

    11. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      Perhaps they did the sensible thing, and link to the built in video framework for things that it supports. That way they only have to provide for those video formats that are unsupported by Core Video.

    12. Re:3 2 1 Takedown by jedidiah · · Score: 5, Informative

      > It's not Apple doing the abusing. It's the GPL that is incompatible with the App Store.

      The GPL predates the App Store by about 20 years. If Apple decided to create terms for it's store that are incompatible with a 20 year old license then that is on Apple.

      It's their decision to be jackasses.

      The rest of us should not bow and scrape and grovel just because Apple has decided it can abuse the rest of us at will.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    13. Re:3 2 1 Takedown by jedidiah · · Score: 1

      The only thing that the LGPL allows that the GPL doesn't is the whole dynamic linking thing. That is not a relevant distinction here. So whatever Apple is doing that could p*ss off a Free Software developer applies equally to the GPL or LGPL.

      The main difference between the two are how derivative works are defined.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    14. Re:3 2 1 Takedown by SuperKendall · · Score: 1

      You can distribute GPL or other open-souce software on the App Store, because it's easy to also distribute source somewhere else.

      As a copyright holder you can only request that the app is removed if distributing it violates the license under which you contributed.

      False, as the copyright holder you can stop someone from distributing your copyrighted work for any reason. That's the reason GPL even works, because it is based on copyright. They had every right to stop VLC from being distributed on iOS - it's just that it also broke the implicit promise they made by letting people use the code under an open-source license. As long as you could get code for the application itself (which you can) then it does not violate the GPL license under which it's being used.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    15. Re:3 2 1 Takedown by xeio87 · · Score: 1

      I was always under the impression the GPL was meant to protect user rights, not creator rights, hence copy"left".

      But if they wanted to shoot their own project in the foot by prohibiting an iOS distribution, I suppose they do have that right. I just retain my right to call it sour grapes.

    16. Re:3 2 1 Takedown by kthreadd · · Score: 1

      You can't take it back once you have given someone code licensed under GPL. They are entitled to distributing it. You can't go to for example Debian and say that they are no longer allowed to distribute your GPL software. You can only say that if they violated the terms in the license.

    17. Re:3 2 1 Takedown by naasking · · Score: 1

      No, LGPL libraries can be distributed in commercial software, and only changes to the library itself, if any, need be open sourced under the LGPL. They don't need permission from anyone to distribute it.

    18. Re:3 2 1 Takedown by kthreadd · · Score: 1

      App developers deserve to distribute their software under their own terms. Apple limits this and the way users are allowed to use the software. This breaks the fundamental principles of free software, which says that you the user should not be dominated by someone else in order to do your computing. Apple does not allow developers to distribute their software under fair conditions.

    19. Re:3 2 1 Takedown by kthreadd · · Score: 2

      It's unhealthy if your goal is to dominate your users. It prioritizes computing freedom.

      Yes it complicates distribution. But if the developers didn't wanted to sign up for that free software thing they should have picked a different licensed.

    20. Re:3 2 1 Takedown by SuperKendall · · Score: 2

      You can't take it back once you have given someone code licensed under GPL. They are entitled to distributing it.

      That is not true. As the copyright holder you in the end have full control over what anyone can do with the source. The GPL is just a promise of what you will NOT do - even though you could.

      Otherwise the code would be public domain, which is exactly the opposite of what the GPL does. The GPL leaves all copyrights firmly in the hands of the original owner.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    21. Re:3 2 1 Takedown by kthreadd · · Score: 1

      Because you know, that's totally the spirit of open source.

      This is the difference between open source and free software. VLC is free software. It has nothing to do with open source.

    22. Re:3 2 1 Takedown by UnknowingFool · · Score: 1

      What are you smoking? A developer ported VLC to iOS. Apple accepted the application. Later one of the original developers of the VLC objected to Apple distributing his code due to licensing concerns. So Apple removed the app. Your position is that Apple should know everything about every single application that is submitted to it? That's as asinine as saying craigslist should know that every item sold using their website is legal and not stolen.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    23. Re:3 2 1 Takedown by Anonymous Coward · · Score: 1

      Only as long as you link _dynamically_. You can't statlink it and then violate the LGPL.

    24. Re:3 2 1 Takedown by UnknowingFool · · Score: 3, Interesting

      App developers deserve to distribute their software under their own terms. . Apple limits this and the way users are allowed to use the software. This breaks the fundamental principles of free software, which says that you the user should not be dominated by someone else in order to do your computing.

      Yes they do but where does it developers have a right to use Apple's store to distribute their software as they wish. Nowhere. You want to write an app and post your source code for the world to see, that's your choice. If you want to use someone's distribution channel you have to abide by their rules.

      Apple does not allow developers to distribute their software under fair conditions.

      Apple does not allow developers to distribute software under your conditions. What you consider fair is not what everyone considers fair. Some developers do not want anyone to see their source code under any circumstances.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    25. Re:3 2 1 Takedown by kthreadd · · Score: 4, Informative

      What are you smoking? A developer ported VLC to iOS. Apple accepted the application. Later one of the original developers of the VLC objected to Apple distributing his code due to licensing concerns. So Apple removed the app. Your position is that Apple should know everything about every single application that is submitted to it? That's as asinine as saying craigslist should know that every item sold using their website is legal and not stolen.

      The original developer objected because it violated the licensed he originally developed VLC under. That simple. You are not allowed to take VLC and do whatever you want with it. You should respect software freedom. If you don't, you don't get to distribute VLC. That's why he could request that the app was pulled, because it did not conform with the license he used.

    26. Re:3 2 1 Takedown by Anonymous Coward · · Score: 1

      I'm not trying to be an asshole but you're just plain 100% wrong. Once you release code as GPL, you can't go back and tell people not to redistribute it. Everyone that got a copy has no legal obligations to you other than those in the GPL (disregarding patent and trademark laws). That means that they are free to distribute it under the terms of the GPL.

      The reason why VLC is not in the app store is because the terms that users agree to when they use the App Store are incompatible with the requirements for redistribution in the GPL.

    27. Re:3 2 1 Takedown by UnknowingFool · · Score: 1

      The original developer objected because it violated the licensed he originally developed VLC under. That simple. You are not allowed to take VLC and do whatever you want with it. You should respect software freedom. If you don't, you don't get to distribute VLC. That's why he could request that the app was pulled, because it did not conform with the license he used.

      Then the person who developed the iOS app should be pilloried and burned alive in the town square. And how is this the fault of Apple again? They got a takedown notice; they complied. Oh, right, because it's Apple.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    28. Re:3 2 1 Takedown by kthreadd · · Score: 1

      And how is this the fault of Apple again? They got a takedown notice; they complied. Oh, right, because it's Apple.

      It's not Apple's fault that it was pulled, but it's partly Apple's fault that it could be pulled. Which is OK, they don't have to allow everything and is fully within their right to impose restrictions on distribution. Just be aware that this is why the GPL was developed, and why software licensed under it will have problems with it.

    29. Re:3 2 1 Takedown by MysteriousPreacher · · Score: 1

      What you said that made sense needed just a few words: The licence was violated - plain and simple. VLC should no more have been submitted any more than GPLed code should be compiled in to Adobe Photoshop. Software freedom? Bullshit, take that trope and keep it in mind when you're outside Wallmart singing The Red Flag.

      Thus isn't about software freedom; it's about licensing. In this context the only thing that should be respected is the licence. If its software freedom, plenty would argue that more permissive licenses are freer than the GPL. But i digress. That is a fucking endless debate, with good and bad arguments on both sides, but definitely not worth dragging in to this discussion. Focus on the matter at hand, brother kthreadd.

      --
      -- Using the preview button since 2005
    30. Re:3 2 1 Takedown by Camembert · · Score: 1

      If I remember well, it is these two facts: - (a smaller one) that the source code is not available through the app store. In my opinion, having the source available on the homepage of the app is good enough. - (the big one): the app store, by the way it works, uses DRM for all apps, even the free ones. 2 persons who want to use VLC on their i device need to download it separately from the app store. You can't simply copy the app from idevice A to idevice B. Does this really matter? It seems that the developer had a problem with it. So Apple took it off the site. However I think it is an overreaction from the developer, in practice the app is easily available for everyone with an idevice. Personally, I am a satisfied user of the app store concept. It works well, smooth updates, no hassle. I think it is more a loss for the VLC team to miss out on the millions of users. So I used other video players - which, I would not be surprised to learn, may well have "borrowed" some decoding routines from the VLC project source... I do hope one improvement: as much as possible decoding through the hardware decoder of the i device, NOT through the processor as it originally did before being pulled. That would make a huge battery life difference.

    31. Re:3 2 1 Takedown by UnknowingFool · · Score: 1

      It's not Apple's fault that it was pulled, but it's partly Apple's fault that it could be pulled. Which is OK, they don't have to allow everything and is fully within their right to impose restrictions on distribution. Just be aware that this is why the GPL was developed, and why software licensed under it will have problems with it.

      Apple probably doesn't give a rat's ass whether or not it got pulled. They were trying to comply with a copyright holder's wishes.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    32. Re:3 2 1 Takedown by Anonymous Coward · · Score: 1

      This is a valid point, since Apple's build tools aren't setup to let you build a dynamic library for iOS.

    33. Re:3 2 1 Takedown by Billly+Gates · · Score: 1

      It is not a problem for software having problems with anything non RMS approved and extreme in ideology? That is a funny sense of the term freedom.

      What about my freedom to charge users? What about my freedom to let do what I like and not what the author of some header file or object I linked too?!

      GPL is a plague and why the BSD license is supperior especially for tax payer funded software where corps can not play. If I develop some software that costs money to develop I need to charge for it or I go out of business.

      The LGPL is perfect. You keep your freedoms and I can link to it and keep mine. Many ignorant develpers think RMS is nuts but have no idea they open businesses and users up to liability by making it GPL. I think it is morally wrong to tell others what to do with software they write. Apple to me is not the bad guy but rather the authors of the header files.

    34. Re:3 2 1 Takedown by SuperKendall · · Score: 1

      That is not an issue in this case, as it merely means they have to provide the source for the VLC app (which they are). The system dynamically loads the application and does not statically link to it, so the actual iOS system being closed does not matter.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    35. Re:3 2 1 Takedown by rsborg · · Score: 4, Informative

      Yeah, lets be clear about this apparently...

      The Dev in question happens to work for a competing phone manufacturer

      The developer's name is Rémi Denis-Courmont [1], and while he's the lead developer for the VLC app, also worked for Nokia at the time, and thus the conflict of interest in his revocation of VLC iOS app.

      [1] http://www.tuaw.com/2011/01/08/vlc-app-removed-from-app-store/

      --
      Make sure everyone's vote counts: Verified Voting
    36. Re:3 2 1 Takedown by harlows_monkeys · · Score: 2

      Apple wasn't the "distributor" in this case, their AppStore was just being used as a Distribution Channel by the VLC Team. So VLC violated GPL by choosing an incompatible Distribution Channel, Apple had nothing to do with it. Stop spreading obvious lies.

      That's not correct. When an end user installs an app via the App Store, software written by, deployed by, and under the control of Apple makes a copy and distributes that copy to the end user. Apple needs the permission of the copyright owner in order to do these things. 17 USC 106.

      Apple is relying on the assurance of the developer of the app that he is either the copyright holder, or has the permission of the copyright owner to grant Apple permission to do those things. If the developer did not have permission, than the developer has violated his agreement with Apple, and if Apple were to get sued and have to pay damages to the copyright owner, they'd almost certainly be able to recover those damages from the developer. However, that's between Apple and the developer. The copyright owner is not required to delve into the relationship between Apple and its developers and ascertain the ultimate party that caused his copyright to be violated and try to get them to stop. He can go after anyone who is making and distributing unauthorized copies, and that includes Apple.

    37. Re:3 2 1 Takedown by Billly+Gates · · Score: 1

      Wrong.

      The GPL forbids you to link to it or develop any software that includes any bits of code in it under any other license.

      Basically if I wrote a silly .dll or header file that is only 1k in length that you include for your 100 meg program I in essence take ownership of the rest of it as the GPL forbids linking it unless the master program is also under GPL.

      The LGPL ( I wish more developers would know and use this) makes linking fine as long as you do not contribute back to me in a non GPL license.

      The GPL restricts freedom of the developer. It is an anti-EULA. EULA means the user gives up rights to the owner. GPL means the owner gives up rights to the user. So it is one extreme or the other and LGPL stays neutral in this.

    38. Re:3 2 1 Takedown by lister+king+of+smeg · · Score: 1

      nope all previously licensed copies and their derivatives retain their license your changes do not apply retro actively only to new copies that you ditribute.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    39. Re:3 2 1 Takedown by SuperKendall · · Score: 1

      Once you release code as GPL, you can't go back and tell people not to redistribute it.

      Yes, you can, you are the copyright holder.

      They can argue that because of the GPL, they do not have to. But that does not mean the original copyright holder has no leg to stand on.

      Everyone that got a copy has no legal obligations to you other than those in the GPL

      The GPL means nothing without copyright under it, therefore copyright is still with the original owner.

      The reason why VLC is not in the app store is because the terms that users agree to when they use the App Store are incompatible with the requirements for redistribution in the GPL.M

      False, we know that's false because there are many GPL based apps in the App Store today. VLC was removed ONLY because one of the original copyright holders, a developer on VLC, complained to Apple.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    40. Re:3 2 1 Takedown by fnj · · Score: 2

      Basically if I wrote a silly .dll or header file that is only 1k in length that you include for your 100 meg program I in essence take ownership of the rest of it as the GPL forbids linking it unless the master program is also under GPL.

      Incorrect. You don't "take ownership" of somebody else's work by default. Copyright rules, legally. Each party owns his own work by copyright. What you have, IF the other guy's work is not GPL, is a case for that guy violating the GPL.

    41. Re:3 2 1 Takedown by fnj · · Score: 1

      One of the developers acted like a dick, and declared "zomg, that benefits a large corporation therefore it's evil, you're in violation of my copyright, take it all down".

      Don't be a clown, you anonymous shill, and especially don't be an ignorant blowhard. The terms of the App Store were in violation of the program's license, not the copyright, except insofar as the copyright is what puts the teeth in enforcing the license terms. It had nothing to do with benefiting a large company. On the contrary, many large corporations benefit from the GPL. Why should you publish license terms (GPL) if you do not intend to have them honored?

    42. Re:3 2 1 Takedown by jrumney · · Score: 1

      If Apple want to be just a distribution channel, and not a distributor, then they need to stop imposing additional licensing terms on the software being distributed through them. By adding their own terms, they are involving themselves in the distribution process.

    43. Re:3 2 1 Takedown by jbolden · · Score: 1

      Apple is the distributor for the app store. Distributors have rather substantial obligations under the GPL.

    44. Re:3 2 1 Takedown by Anonymous Coward · · Score: 1

      I don't understand how they think this will work. LibVLC is LGPL, and unless they got consent from _every_ VLC contributor or the terms and conditions changed dramatically the last couple of months they can't distribute it on the iOS App Store..

      Yes, they got consent from _every_ VLC contributor because this release is by VideoLAN not that other company (which shall not be named) that released it last time in violation of the license. This article does not make that clear - in actual fact this is the first official VLC release for iOS. Source code with dual license is available at http://www.videolan.org/vlc/download-ios.html

      VideoLAN has contributor agreements and owns the copyright, they can change the license.

    45. Re:3 2 1 Takedown by Kielistic · · Score: 1

      What about my freedom to let do what I like and not what the author of some header file or object I linked too?!

      You are perfectly free to not use that header file and write your own software. Or do the developer's rights not matter to you if it gets in the way of you making money off their work?

      GPL is a plague and why the BSD license is supperior especially for tax payer funded software where corps can not play. If I develop some software that costs money to develop I need to charge for it or I go out of business.

      Wait, is it public funded or are you making it to sell it? Because if it's tax-payer funded you are getting paid to write it.

    46. Re:3 2 1 Takedown by jbolden · · Score: 1

      They charge money for licenses, manage relicensing, and handle accessories sales. They are so far over the line in being a distributor it isn't remotely questionable.

    47. Re:3 2 1 Takedown by Kielistic · · Score: 1

      The GPL means nothing without copyright under it, therefore copyright is still with the original owner.

      we know that's false because there are many GPL based apps in the App Store today

      I wrote softwareX- I hold the copyright. I am free to license softwareX to Fred under the GPL. I am also free to license softwareX to Greg under a license I make up on the fly. Fred still has a GPL license to softwareX.

      If the owners of the copyrights to GPL softwareY want to allow their software on Apple's AppStore even if it doesn't fully comply with the GPL license they are free to do so. That does not mean that the Apple AppStore complies with the GPL. As we see here, if a copyright holder does not allow the re-licensing to allow it there it will get removed.

    48. Re:3 2 1 Takedown by Kielistic · · Score: 1

      That is not a problem to the people that wrote the GPL. If you want to make use of the hard work of others then you have to pay them their due. They demand the price of having your software also benefiting others.

      If what you are linking is so trivial that you don't think it should be able to control the licensing of your software don't use it. Write it yourself like everyone else has to.

    49. Re:3 2 1 Takedown by Kielistic · · Score: 3, Interesting

      What you consider fair is not what everyone considers fair. Some developers do not want anyone to see their source code under any circumstances.

      Those two things are not mutually exclusive as you frame them. In fact, every other platform manages to accommodate both.

      Yes they do but where does it developers have a right to use Apple's store to distribute their software as they wish. Nowhere.

      Perfectly true. And the developers of GPL software have every right to have their work removed from Apple's store and encourage others to do the same. Somehow I think no GPL software in the ios ecosystem would be more harmful to the ios usebase than it would be to writers of GPL software.

    50. Re:3 2 1 Takedown by Kielistic · · Score: 1

      That's quite the persecution complex you have there. It would certainly help OSS ideals if he managed to convince every other GPL author to do the same. Perhaps this person actually believes in the software freedom they contribute to?

    51. Re:3 2 1 Takedown by i.r.id10t · · Score: 1

      It actually isn't even the app store's fault - the blame rests on the marketing/development/sales folks who had the engineers who designed the OS software lock it down to only getting applications from one particular source. It is part of their operating model - they aren't just selling a physical device, or some bits on a disk, they are selling an end user experience. And in order to make that happen the way they envision it, they have to maintain as much control as possible.

      --
      Don't blame me, I voted for Kodos
    52. Re:3 2 1 Takedown by Billly+Gates · · Score: 2

      You should read the clauses of the gpl? Any linking is part of a deritive work and not allowed. This is why Sun couldnt gpl java for IceTea as it would be useless in a commercial setting.

      A special classpath exception was added. Lgpl lets people link freely and the stuff spewed on slashdot is incorrect. If you release gpl apis do not be surprised if people cant use it and replace yours lile what VLC had to do.

      Yes corps pay taxes too and they have the right to use it as much as you. GPL is am ideology that is impractical

    53. Re:3 2 1 Takedown by Billly+Gates · · Score: 1

      So then it is not free?

      The original arguement was gpl is the best oh yeah with a few squeely cheerleaders thrown in and how it bests everyone yada yadA.

      Well it had one developer hold the vlc project hostage! It is not free. 90% of developers who release it under gpl have no clue it adds liability if they use it at work.

      I wont use your software fine. But dont be surprised when you invent the next ruby on rails and people use an inferior clone instead. BSD and Mozilla are more free

    54. Re:3 2 1 Takedown by harlows_monkeys · · Score: 2

      That permission is granted on submission by the Developer.

      Only the copyright holder, or someone authorized by the copyright holder, can grant that permission. If someone else tries to do so, the grant is not effective.

    55. Re:3 2 1 Takedown by psergiu · · Score: 4, Insightful

      One of the VLC devs requested to have it removed because of licensing after said developer was hired by Nokia.
      Note that same developer has not complained over VLC being distributed for Nokia phones under similar conditions with Apple's AppStore.

      --
      1% APY, No fees, Online Bank https://captl1.co/2uIErYq Don't let your $$$ sit in a no-interest acct.
    56. Re:3 2 1 Takedown by Xest · · Score: 2

      "Yes they do but where does it developers have a right to use Apple's store to distribute their software as they wish. Nowhere."

      Flip that around from the users perspective and ask why the user when they buy an iPhone doesn't have the right to run the software they want to run and only the software Apple lets them run from the only official app source.

      Who gives a fuck what Apple thinks, if Apple has only given that single official avenue to end users to install apps then users should be able to install the apps they want from it, or Apple should enable side-loading. It's not a question of Apple's rights, it's a question of users right to be able to use the device they've bought with the software they want to use.

      There's no problem with abiding by Apple's distribution channel if there are alternatives, but Apple can't make it's app store the only legitimate distribution channel and then restrict what people can and can't do on it and expect not to be called out on that.

      "What you consider fair is not what everyone considers fair. Some developers do not want anyone to see their source code under any circumstances."

      What are you on about? Allowing GPL code on the app store wouldn't force every other app to suddenly become GPL...

    57. Re:3 2 1 Takedown by serviscope_minor · · Score: 1

      No it's not.

      Er yes it is. It is entirely Apple's fault. They were fully aware of the GPL and decided to make terms incompatible with is. They have no oblication not to do this, but it doesn't make it their fault and does not absolve them of responsibility.

      --
      SJW n. One who posts facts.
    58. Re:3 2 1 Takedown by serviscope_minor · · Score: 1

      What about my freedom to charge users?

      Firstly the GPL doesn't prevent that.

      Secondly you seem to want to use some random developer's code for your own purposes without paying him. You sound nothing like a piece of whiny, leeching scum. You're always complaining that GPL code authors aren't giving you free stuff.

      If you don't like the GPL then just pretend that nothing based on the GPL exists. Problem solved.

      --
      SJW n. One who posts facts.
    59. Re:3 2 1 Takedown by MachineShedFred · · Score: 1

      And Apple took it down because he was right.

      So Apple's the bad guy for actually respecting the original developer's rights?

      --
      Slashdot still doesnâ(TM)t support Unicode after it was added to the HTML standard in 1997.
    60. Re:3 2 1 Takedown by UnknowingFool · · Score: 1

      Flip that around from the users perspective and ask why the user when they buy an iPhone doesn't have the right to run the software they want to run and only the software Apple lets them run from the only official app source.

      Then they can buy Android. It's not like Apple has made it a secret that they have a walled garden. Developers don't have a write to dictate to their terms to Apple or Google or whoever.

      Who gives a fuck what Apple thinks, if Apple has only given that single official avenue to end users to install apps then users should be able to install the apps they want from it, or Apple should enable side-loading. It's not a question of Apple's rights, it's a question of users right to be able to use the device they've bought with the software they want to use.

      Users don't have to buy Apple at all. Is it that hard to grasp? I don't like the server choices that MS or Apple offers; I run a Linux server at home.

      What are you on about? Allowing GPL code on the app store wouldn't force every other app to suddenly become GPL...

      Are you following this topic at all? Apple allowed GPL code on their store. One of the copyright holders objected to his code being on the store that someone else had ported to iOS. So Apple removed it at his request. Apple probably doesn't give a damn whether it was GPL or not only that copyright law was being followed.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    61. Re:3 2 1 Takedown by UnknowingFool · · Score: 1

      Those two things are not mutually exclusive as you frame them. In fact, every other platform manages to accommodate both.

      See above: "You want to write an app and post your source code for the world to see, that's your choice."

      And the developers of GPL software have every right to have their work removed from Apple's store and encourage others to do the same.

      Which Applied complied with. Suddenly they are anti-GPL because they complied with a copyright holder's wishes. Instead others would have rather Apple change their policies that were well known.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    62. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      Er yes it is. It is entirely Apple's fault. They were fully aware of the GPL and decided to make terms incompatible with is. They have no obligation not to do this, but it doesn't make it their fault and does not absolve them of responsibility.

      Complete nonsense. Commercial software distributed as binaries predated the GPL. It was the GPL that was set up to try and disrupt that. It's author's intent was to stop distribution of simple binary software. That attempt is failing.

      Apple created a commercial software store, that just as has been done since times long before the GPL, distributed software binaries. For money and for free.

      It's completely agnostic to open source and the GPL. There's nothing to stop a developer distributing source for their app, either on their own website, or as an option to view/export or whatever the source from within the app. No Apple rules get in the way at all. But it's not source code distribution platform in itself. It's a software binary distribution business. That's the nature of it.

      The thing that stopped VLC first time around was one of it's developers (who happened to be a Nokia employee) complaining about the other VLC developers that put it on the App Store. His interpretation of the GPL right to wrong is that the source, as text, should be downloadable from within the App Store.

      If there is "fault", it's the GPLs, and it's adherents. Again, none of this is Apple's doing. As far as Apple is concerned VLC could have been there all along, just as plenty of other GPL software is.

      The idea that people like you try to perpetuate, that Apple wrote rules within the App Store terms intended to exclude GPL is pure myth.

    63. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      App developers deserve to distribute their software under their own terms.

      App developers don't deserve anything. They are business people that take attractive opportunities where they present themselves. And vast numbers of them have seen the Apple App Store as a huge opportunity. And they chose that opportunity knowing how the App Store works.

      Apple limits this and the way users are allowed to use the software. This breaks the fundamental principles of free software, which says that you the user should not be dominated by someone else in order to do your computing.

      It does no such thing. If an app developer wants to distribute his code, he can host it on his own website. There's a link to his website from the Apple App Store page.

      Indeed many people's reading of the GPL is that there is no problem putting it on the Apple App Store. Many GPL apps are already there.

      The problem with GPLers is that are trying to be disruptive to the established software distribution methods that long preceeded the license. But they seem to think they deserve everyone to change to suit them and their ways. But they don't. Basically GPL is a religion, full of people that demand every other way is wicked, and everyone must follow their holy document. They're cranks.

    64. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      It's not Apple's fault that it was pulled, but it's partly Apple's fault that it could be pulled.

      No it's not. Apple has a legal duty to act on a DMCA takedown notice.

      And even if that were not the case, it would be be a heap of bad, legally and morally if the authors of apps couldn't get their apps taken off sale if that's what they want.

    65. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      "What about my freedom to charge users?"
      Firstly the GPL doesn't prevent that.

      You understand that, and yet you don't understand that the App Store doesn't prevent GPLed software from being put on it. Wilful ignorance is not an argument.

      Secondly you seem to want to use some random developer's code for your own purposes without paying him.

      It's not very free if developers are obligated to pay for it. There's nothing wrong with non-free software. put don't pretend it's free if it's not.

      If you don't like the GPL then just pretend that nothing based on the GPL exists.

      That's exactly what most professional developers do. It's treated as a virus.

    66. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      No one has any obligations under the GPL. It's not a law. It's a non legal document written by a freak.

      Distributors only have obligations under copyright.

    67. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      The developer canceling the original VLC is just exhibiting petty Apple-hatred, not helping open source (or the people who use it) in any way.

      Well, as a Nokia employee it was more like petty point scoring for his own company vs a competitor.

    68. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      The license did not allow distribution under unfair conditions. Distributing the app in the app store implied unfair conditions.

      You're being vague. What specific point of the GPL prevented it from being distributed in the App Store.

      Just because you're a copyright holder doesn't mean that you can do that, it has do actually be distributed against your license.

      Of course a copyright holder can stop their app being distributed. They don't need to have any license at all. Of course they might hold a contract with a publisher that guarantees the publisher a certain period of distribution. But then they are being bound by the contract, it's not that he doesn't have the fundamental right to control of copies being made of his work.

    69. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      The terms of the App Store were in violation of the program's license

      In what way, specifically?

    70. Re:3 2 1 Takedown by jbolden · · Score: 1

      It is a legal document and as it has a culture around it it likely is an entire forum. Which means "the freaks" words and those who agree with them have force when it comes to interpretations.

      As for distributors of course they obligations under copyright and one of those is to distribute only things they have license to under the terms of the license.

    71. Re:3 2 1 Takedown by Kielistic · · Score: 1

      They are anti-GPL because their policies do not allow compliance with the GPL. They do not allow GPL software on their platform. GPL software must be re-licensed before it can be put into the store. I am sorry "anti-GPL" sounds negative towards Apple and causes cognitive dissonance in you but how else would you like it put? "Counter-GPL"? "Un-GPL friendly"? "In direct conflict with the ideals of the GPL"?

      Of course others want Apple to change their policies. A good portion of people think their policies are bullshit. The whole point of the GPL is to make computing open. It only stands to reason that the same people would want to get Apple to change their policy on un-open computing.

    72. Re:3 2 1 Takedown by Kielistic · · Score: 1

      It's funny that you think a developer held the project hostage for wanting it to be in compliance with the terms they contributed under. Could it not be that Apple is actually holding the device you paid good money for hostage? It's them that aren't allowing you to install any software unless you play by their rules and pay them their toll.

      I'm going to completely ignore your little "free" diatribe because I know you've had it explained to you dozens of times. The concept and meaning of the word "Free" to the FOSS movement is presented loudly and repeatedly anywhere FOSS lands. So you either have no idea what you are talking about or are being dishonest.

    73. Re:3 2 1 Takedown by Kielistic · · Score: 1

      Yes corps pay taxes too and they have the right to use it as much as you

      Yeah! you're right. They, in fact, have the exact same right to use it as I do. Which is all nicely defined in the GPL license.

      GPL is am ideology that is impractical

      Seems to be doing pretty well though.

    74. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      It is a legal document and as it has a culture around it it likely is an entire forum.

      Culture?!

      It's not a legal document. It has no standing in the law. Copyright does.

      Some people might interpret the GPL as giving them the copyright holder's permission to distribute the item in question. And they might argue that in court. But as it stands there's no guarantee. The person that put the GPL on the item might not have the copyright on it all. And if they don't, the GPL won't save you.

    75. Re:3 2 1 Takedown by jbolden · · Score: 1

      Yes culture. In contract law forms are determined by a cultural meaning.

      As for no standing in law, all licenses have standing in law. As for the GPL not saving you, the issue of copyright fraud has been tried repeatedly. If you distribute believing yourself to be properly licensed you are only responsible for marginal fees at worst. The person who put a fraudulent GPL on code they aren't entitled to would be the one who has trouble, same as any other false license.

    76. Re:3 2 1 Takedown by BasilBrush · · Score: 1

      As for no standing in law, all licenses have standing in law.

      No they don't.

  2. DMCA by Russ1642 · · Score: 1

    Sony will come after them for copyright infringement.

    1. Re:DMCA by Em+Adespoton · · Score: 1

      Sony will come after them for copyright infringement.

      I presume they didn't link LibDeCSS in this build.... ...but what about the patent infringements? Or are those waived since Apple already licenses the appropriate patents and this is distributed by Apple?

  3. Bi-Licensed? by Luthair · · Score: 3, Informative

    It's dual licensed you insensitive clod!

  4. how long before HBO asks apple to take it down? by Joe_Dragon · · Score: 5, Funny

    how long before HBO asks apple to take it down?

    1. Re:how long before HBO asks apple to take it down? by Savage-Rabbit · · Score: 4, Informative

      how long before HBO asks apple to take it down?

      The irony is that VLC was pulled from the iTunes store last time not by evil Sith lord apprentices at Apple, not at the behest of a evil DRM purveyor, nor was it pulled due to threats by the RIAA or MPAA, it was removed at the insistence of a VLC developer because he felt that the GNU general public license conflicted with the iTunes App Store license. Apple was apparently not bothered by this until this guy raised a stink about perceived GPL violations, so just this once the evil corporate weasels seem to be blameless. Perhaps this sorry saga also explains the license changes?

      --
      Only to idiots, are orders laws.
      -- Henning von Tresckow
    2. Re:how long before HBO asks apple to take it down? by UnknowingFool · · Score: 1

      Apple was apparently not bothered by this until this guy raised a stink about perceived GPL violations.

      I think another way to look at it that Apple doesn't check on the licensing of any code that is submitted. It assumes that all code submitted falls under a permissible license. When someone objected, they removed the app.

      --
      Well, there's spam egg sausage and spam, that's not got much spam in it.
    3. Re:how long before HBO asks apple to take it down? by serviscope_minor · · Score: 1

      so just this once the evil corporate weasels seem to be blameless.

      Not even slightly blameless. The evil coprorate weasles constructed GPL incompatible rules in the first place.

      For some reason whenever anyone else points this out you get a storm of protest about how it's their right to be evil corporate weasles. It certainly is their tight, but they're still evil corporate weasles.

      --
      SJW n. One who posts facts.
  5. Exciting news? by Arker · · Score: 5, Insightful

    Yeah, this doesnt seem like exciting news to me at all. Dual-licensing it to get it in the app store is a failure, not a victory. If the app store isnt compatible with GPL software, then the app store shouldnt be getting access to GPL software. Dual-licensing to work around Apples error seems actively counterproductive to me.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
    1. Re:Exciting news? by EvanED · · Score: 1

      To play devil's advocate for a second:

      Yeah, it's way better to screw your users over something that you have a smaller chance of affecting than you have of seeing some pigs aloft over a week-old snowball in hell.

    2. Re:Exciting news? by gnasher719 · · Score: 2

      Yeah, this doesnt seem like exciting news to me at all. Dual-licensing it to get it in the app store is a failure, not a victory. If the app store isnt compatible with GPL software, then the app store shouldnt be getting access to GPL software. Dual-licensing to work around Apples error seems actively counterproductive to me.

      The question is not whether the app store is compatible with GPL software. The question is whether a copyright holder asks Apple to remove the software. It's a DMCA notice, and when Apple gets a DMCA notice, they take it down. The strange thing is that on Slashdot a DMCA takedown notice is considered a dick move - unless it is about GPL licensed software taken down from the app store.

    3. Re:Exciting news? by 93+Escort+Wagon · · Score: 2

      Yeah, this doesnt seem like exciting news to me at all. Dual-licensing it to get it in the app store is a failure, not a victory. If the app store isnt compatible with GPL software, then the app store shouldnt be getting access to GPL software. Dual-licensing to work around Apples error seems actively counterproductive to me.

      Problem is you've got it backwards. The problem wasn't from the point of view of Apple's license... it was from the GPL end. It was a VLC developer that requested it be removed.

      There is lots of GPL licensed software on the iOS App Store - Apple doesn't care at all.

      Now if you believe the GPL is incompatible with Apple's licenses AND if you think somehow that is Apple's problem... well, then, Ballmer had a point when he referred to the GPL as a "cancer".

      --
      #DeleteChrome
    4. Re:Exciting news? by GameboyRMH · · Score: 1

      This. This is a loss for FLOSS.

      And how is this not still a GPLv2 violation?

      http://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    5. Re:Exciting news? by GameboyRMH · · Score: 1

      The conflicting portion of the GPL here is not a shortcoming. It is a very intentional and IMO positive part of its design. Sad that they're trying to work around it. As far as I can tell this is still a GPLv2 violation though:

      http://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    6. Re:Exciting news? by kthreadd · · Score: 1

      Apple doesn't care, but anyone who have contributed to them that cares can request that they are pulled since they are distributed against the conditions stipulated in the GPL.

    7. Re:Exciting news? by dfghjk · · Score: 2

      If it's dual-licensed it's not GPL software, the owners of the copyright can do as they wish. What do GPL advocates say? Oh yeah...if you don't like it, write your own.

      "Actively counterproductive" implies that you know what the definition of "productive" is in the authors' minds. Clearly you don't.

    8. Re:Exciting news? by Arker · · Score: 1

      "It was a VLC developer that requested it be removed."

      Correct. Because it was being distributed in violation of copyright law. Best I can tell, that is still the case.

      "There is lots of GPL licensed software on the iOS App Store - Apple doesn't care at all."

      Of course they don't, they have never cared about copyright (as long as it's someone elses copyright.) And the availability of GPL software in the App Store is to their advantage - it adds value to their product without costing them anything. I am sure they would love to have more of it.

      But they are not entitled to it. The GPL is clear - you can distribute GPL software, or impose the kind of terms that the Apple store imposes, but you cannot do both. Apple has made their choice and it is not compatible with free software at all, so they should not be able to reap the benefits they are not entitled to here.

      "Ballmer had a point when he referred to the GPL as a "cancer"."

      He was projecting. It's a common psychological coping mechanism. The GPL is actually an anti-cancer. It cant kill cancer (unfortunately) but it reveals it and hinders it by refusing to mix with it, by design. Naturally the cancer doesnt like this.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    9. Re:Exciting news? by Arker · · Score: 1

      The users here are screwed no matter what, and it's Apple doing the screwing either way. Encouraging them to continue going back to Apple for more abuse is a worse screwing than removing your video player though, by orders of magnitude.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    10. Re:Exciting news? by fnj · · Score: 1

      The question is not whether the app store is compatible with GPL software. The question is whether a copyright holder asks Apple to remove the software. It's a DMCA notice, and when Apple gets a DMCA notice, they take it down.

      Dear god, how did the world survive before DMCA? Oh wait, copyrights were enforced via due process rather than draconian excess. How will the world survive after DMCA is blown away and sent back to hell where it came from? I'm confident the answer is "very nicely; a lot better than now in fact". The DMCA is a red herring to this situation. A copyright holder can defend against violation of the terms of the license he has chosen without the DMCA.

      The strange thing is that on Slashdot a DMCA takedown notice is considered a dick move - unless it is about GPL licensed software taken down from the app store.

      I don't think there is a single voice here, except that the DMCA is the wrong way to enforce copyrights, prosecutes violations the wrong way (criminally), prescribes the wrong penalties, and glosses over due process. Some of us don't think there is such a thing as intellectual property; others think that copyright is proper but that software patents are bad policy; others that all patents are bad policy. Some of us (to grossly oversimplify) prefer GPL; others prefer BSD or something else; others think there is a benefit to mixing licenses for different components.

    11. Re:Exciting news? by BasilBrush · · Score: 1

      As far as I can tell this is still a GPLv2 violation though:

      Which doesn't matter now that VLC is dual licensed. So long as the Mozilla license is compatible, they're fine.

      Of course they need the permission of all the authors of code included in the iOS bundle to add that Mozillsa license. Which explains why some of it was rewritten. Clearly they've rewritten the bits where either the authorship is not clear, or the authorship is known but permission to add the Mozilla license was not given.

  6. GPL incompatible with the app store!?! by MobyDisk · · Score: 4, Informative

    This was news to me, and every news article just vaguely mentions it without providing details. For those unfamiliar, here is an article by the Free Software Foundation explaining the incompatibility. and here is another article which represents a more nuanced position.

    1. Re:GPL incompatible with the app store!?! by GameboyRMH · · Score: 1

      You assumed they weren't wildly incompatible!?

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    2. Re:GPL incompatible with the app store!?! by kqs · · Score: 1

      Huh; I had heard about the "incompatibility" but I didn't know exactly what it was. Thanks for the link.

      It's ironic that a group of people who often hate copyrights and patents will simultaneously cling to a particularly strict interpretation of a App Store/GPL license interaction. I'm not saying the interpretation is wrong, but it;s unclear enough that neither side would want the court battle needed to settle it.

      This definitely sounds like a "cut off the nose to spite the face" situation to me.

  7. support for remote streaming? by MMC+Monster · · Score: 3, Insightful

    Don't particularly care about the licensing issues.

    My question is whether it will allow me to stream from my home system, or will I have to upload every video file or use Dropbox or some other kludge.

    --
    Help! I'm a slashdot refugee.
    1. Re:support for remote streaming? by BenJeremy · · Score: 1

      Plex is a media server, not a client, right?

      He's asking if VLC for iOS will play back DLNA-served media. As another iPhone/iPad owner with a DLNA server that holds all my media, I'd like to know too. Every TV in my house handles media streamed from the Linux box I have in my basement just great... it would be spiffy if I could also watch shows on my tablet so I can sit outside on my deck.

    2. Re:support for remote streaming? by Anonymous Coward · · Score: 1

      Plex has both client and server components.

      There are official clients for Win/Mac/iOS/Android/Samsung TV/LG TV/Roku and other platforms. Unofficial clients (or proxies) exist for still more platforms. All official clients support streaming, optionally transcoded playback from both local and remote servers. On clients with local storage "sync" services are also provided to allow offline playback.

      The server runs on Win/Mac/Linux (x86 and ARM), and the Android and iOS clients have limited server support as well (to re-share synced content). It throws out local media via an HTTP interface, tracks metadata, handles transcoding for limited clients or bandwidth, etc. It supports automatic discovery from any client on the broadcast network (i.e. LAN). It also supports (but does not require) a registration system to allow remote clients to find your server over the Internet (essentially an application-specific version of DynDNS).

      The server also provides DLNA services on the local network, to make all of your Plex goodness available to DLNA devices without a special client, as well as a web interface for a no-install client in any browser with support for HTML5 video or JWPlayer (i.e. flash).

    3. Re:support for remote streaming? by BenJeremy · · Score: 1

      Not interested in the Plex server, as I already have DLNA server software running (for a couple of years) that works well with everything.

      As for the client, I see "Plex" in the App Store... for $4.95. Call me cheap, but I'd prefer a free client. I've contributed enough media playback code to the world to not feel too guilty about it, and I've contributed money to VideoLAN (as I do most "free" software efforts I make use of).

    4. Re:support for remote streaming? by jcupitt65 · · Score: 1

      From the linked article:

      Furthermore, in addition to the original feature set, VideoLAN has added more ways to synchronize media (upload over Wi-Fi, native Dropbox integration, support for third-party apps through the Share dialog, and via Web download), support for network streams, video filters, passcode lock, background audio playback, and playback speed manipulation. There is also support for subtitles (including Closed Captions and complex SSA), native support for multiple audio tracks, and playback on external screens or AirPlay.

  8. Gratuitous license are revocable by DragonWriter · · Score: 1

    > As a copyright holder you can only request that the app is removed if distributing it violates the license under which you contributed.

    Or if you contributed it under a gratuitous license rather than a contracted-for license, since gratuitous licenses are revocable at will.

    1. Re:Gratuitous license are revocable by cduffy · · Score: 1

      Under which country's law?

      In most places, I'd expect promissory estoppel to apply.

    2. Re:Gratuitous license are revocable by DragonWriter · · Score: 1

      > Under which country's law?

      The United States (I think this is a common law principle of licenses not specific to copyright, so it may apply in other common law jurisdictions, to the extent that copyright licenses have not subsequently been excepted from the general principle.)

      > In most places, I'd expect promissory estoppel to apply.

      Promissory estoppel is, as I understand it, limited; generally, it restricts the ability of a party to seek remedies from another party where the second parties action was taken in foreseeable reliance on a promise of the first party to the extent necessary to prevent injustice, it might to an extent, and for a period, mitigate the effect of revocation of a gratuitous license. I've never heard of a case of it being held to make a gratuitous license permanent in the face of the licensor acting to revoke it,

    3. Re:Gratuitous license are revocable by cduffy · · Score: 1

      Which licenses, precisely, are you describing as "gratuitous"? Consideration is, after all, not a hard thing to find.

      In the case of software using copylefted dependencies, the ability to use 3rd-party similarly licensed code is consideration for release the license. In the case of software under more permissive licenses, there's an argument to be made that public assistance in the development of same (bug reports, community support assistance, etc) acts as consideration for the license. If a single peppercorn is sufficient to establish compensation under common law, surely a well-researched bug report is worth more.

      You ask for an example of a case when a "gratuitous" license (a term implying that absolutely no consideration is given, which I deny is the case in the situations given here) was not allowed to be withdrawn. Frankly, I'm not familiar with a single instance in which an OSI-approved license has been withdrawn in a US jurisdiction with respect to previously released codebases -- and were this a feasible thing, we'd have seen Oracle, SCO and others doing no end of it (particularly in the time period in which Microsoft was willing to spend money on convincing the world that using open source software in business was high-risk, and certainly had the funds to buy companies which owned copyright to the codebases of major OSS infrastructure, either directly or by proxy).

      I'd be curious to hear about a case of revocation of an OSI-approved license being held valid in a US court, should such exist -- and suspect that, if one did make it to appeals, we'd be seeing the OSI and their friends weighing in as amici; it'd certainly be an interesting read.

  9. That's not why by SuperKendall · · Score: 1

    anyone who have contributed to them that cares can request that they are pulled since they are distributed against the conditions stipulated in the GPL.

    The reason Apple listens is not complaints about the GPL, but because they are partly the copyright holder. Apple doesn't care about the GPL; they do care about copyrighted work being distributed without permission.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
    1. Re:That's not why by kthreadd · · Score: 1

      You have permission as long as you follow the terms stipulated in the GPL. But it's true that Apple doesn't have to care about that, they can kick your app out for any other reason if they want to.

    2. Re:That's not why by SuperKendall · · Score: 1

      You have permission as long as you follow the terms stipulated in the GPL.

      Technically according to the contract, yes you do.

      However all Apple sees is an original copyright holder issuing a complaint. It's not Apple's job to interpret a contract, it's Apple's job to take down something if a valid copyright holder asks them to.

      --
      "There is more worth loving than we have strength to love." - Brian Jay Stanley
    3. Re:That's not why by Arker · · Score: 1

      "Technically according to the contract, yes you do."

      There is no contract. It's a license, a one-sided grant, not a two-party agreement.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:That's not why by jrumney · · Score: 1

      You have permission as long as you follow the terms stipulated in the GPL. But it's true that Apple doesn't have to care about that,

      They do have to care about that, because they are the ones doing the distributing and imposing the additional restrictions that violate the GPL.

    5. Re:That's not why by tlhIngan · · Score: 1

      They do have to care about that, because they are the ones doing the distributing and imposing the additional restrictions that violate the GPL.

      WHAT restrictions?

      That's the thing - VLC is/was (L)GPLv2.

      The source code to VLC for iOS was always available, which I guess could technically violate the GPL since it's not Apple distributing the code (unless the developer embedded it in the .ipa file...). But that's it, really.

      If you say you can't compile the source and use it on the device - well, $99 says you can, or jailbreaking. Or well, what clause does that violate on the GPLv2?

      It's called TiVoization after TiVo Inc., locked up the kernel and filesystem after a bunch of TiVo hackers bricked their machines and did warranty claims, and the GPLv2 has allowed it.

      It may violate the SPIRIT of the GPL, but not the letter of the license. It's why the GPLv3 is so toxic - because it gets rid of TiVoization, and that makes it ironically incompatible with GPLv2! (Because GPLv3 code imposes additional restrictions on GPLv2 code. The only way you can combine v2 and v3 code is if the v2 code is v2+ (version 2 or later). v2-only and v3 are incompatible, and fun happens if you have a mixed codebase of v2/v2+ and try to add v3 code.

      NOTE: GPLv3 is incompatible with all app stores - Apple's, Amazon's, Google's (Play Store has been adding DRM as of 4.2), Microsoft's, Valve's (Steam), ...

    6. Re:That's not why by jrumney · · Score: 1

      WHAT restrictions?

      Just one example (as I can't be bothered going and reading through the 80 odd pages of legalese that you have to agree to before you use the app store); the additional restriction that you may only deploy any application that you download from the app store on a maximum of 5 devices.

    7. Re:That's not why by BasilBrush · · Score: 1

      Apple don't have to care about the GPL. It's not a law. Copyright is the law, and that's what they need to observe.

      And what restrictions? Which Apple ones, which GPL ones? Do you even know?

    8. Re:That's not why by jrumney · · Score: 1

      Only the GPL gives Apple the right to distribute code licensed under the GPL. Copyright law does not give them any distribution rights, so yes they do need to care about the GPL (or any other license applied to code distributed through the App Store that is not entirely written by the person or company that is submitting it).

      GPL: 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

      Apple: APP STORE PRODUCT USAGE RULES

      (i) If you are an individual acting in your personal capacity, you may download and sync an App Store Product for personal, noncommercial use on any iOS Device you own or control.

      (ii) If you are a commercial enterprise or educational institution, you may download and sync an App Store Product for use by either (a) a single individual on one or more iOS Devices used by that individual that you own or control or (b) multiple individuals, on a single shared iOS Device you own or control. For example, a single employee may use an App Store Product on both the employee's iPhone and iPad, or multiple students may serially use an App Store Product on a single iPad located at a resource center or library. For the sake of clarity, each iOS Device used serially by multiple users requires a separate license.

      (iii) You shall be able to store App Store Products from up to five different Accounts at a time on a compatible iOS Device.

      (iv) You shall be able to manually sync App Store Products from at least one iTunes-authorized device to iOS Devices that have manual sync mode, provided that the App Store Product is associated with an Account on the primary iTunes-authorized device, where the primary iTunes-authorized device is the one that was first synced with the iOS Device or the one that you subsequently designate as primary using the iTunes application.

    9. Re:That's not why by BasilBrush · · Score: 1

      It's irrelevant. The person uploading it claims they have the rights to distribute it. They may be claiming that wrongly or fraudulently, but that's a case of copyright law, not the GPL.

  10. Re:LGPL is compatible by Billly+Gates · · Score: 1

    GNu is not. Hence why Bill Gates called it viral and started a flamewar on slashdot. I am not a troll here but someone correct me if I am wrong?

    If I make a C++ header file it means you can use include in your mozilla or proprietary product if I make it available under the LGPL. L = linking. You acknowledge you do not own my header file and likewise I do not own your program. You own the program even if I provide the header file, dll, or .so you wish to use to make it functional.

    Now if I make it under the GPL I can sue you for copyright violations as the GPL dictates if one part of the program is GPL then all of it is. RMS did this because he hates non free software and this now puts you in a sticky situation.

    This is why FSF put a linking exception in the GPL license for IcedTea. Java developers can not use a gnu library in a non-gnu program.

  11. You are ignoring what I said by SuperKendall · · Score: 3, Informative

    Why are you so ashamed of your thinking that you post AC? You actually had a pretty good post there.

    Your understanding of the GPL is roughly correct. Your understanding of what I said is utterly wrong.

    Yes the GPL is a contract, but like any contract the actual enforcement is up to the courts. It does not mean the original copyright holder cannot sue someone for using source code that was distributed under the GPL, or make complaints to others that as the copyright holder (for instance) they wish to have something removed from the app store. That's exactly what happened. Apple complied because the person who complained was the copyright holder - end of story.

    As you say actual compliance with the GPL is spotty but it doesn't matter as long as no-one takes action. The VLC app would have stayed on the app store until the end of time if one of the copyright holders did not complain.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  12. $1,045 by tepples · · Score: 1

    If you have a problem with the lack of OpenSource Apps for iOS, blame the Developers

    Making use of the open-source aspect of such apps costs $1,045: $649 for a Mac mini on which to run Xcode and $99 for each of four years of the expected service life of the iPod touch, iPhone, or iPad. I blame only Apple's business decisions for this price.

    Users have a CHOICE to not use Apple products

    What you say appears not to be true of a high school student who received an iPod touch, iPhone, or iPad as a gift and is prohibited by law from working.

    1. Re:$1,045 by berj · · Score: 1

      I'm at a loss as to why you include the cost of the Mac mini. Do other computer brands come for free?

      Can you develop for Linux (open source or otherwise) without paying for a computer?

  13. This by The+Cat · · Score: 1

    This thread is the butthurt olympics.

  14. Installation Information by tepples · · Score: 1

    You can distribute GPL or other open-souce software on the App Store, because it's easy to also distribute source somewhere else.

    I thought the iOS developer terms prohibited developers from disclosing "Installation Information" (GPLv3 term) or "scripts used to control [...] installation of the executable" (GPLv2 term) to more than a few dozen people at once.

  15. Then why is DFSG identical to OSD? by tepples · · Score: 1

    VLC is free software. It has nothing to do with open source.

    The free software and open source movements arise from different premises, but they end up at the same conclusion. The Debian Free Software Guidelines and the OSI Open Source Definition are worded nearly identically.

  16. Installation Information by tepples · · Score: 1

    In my opinion, having the source available on the homepage of the app is good enough.

    GPLv3 requires the source code to include what it calls "Installation Information". (GPLv2 has a similar provision about scripts used to control installation.) Apple doesn't let a single developer distribute Installation Information to more than 99 members of the public.

  17. Robo-DMCA false positives by tepples · · Score: 1

    The irony is that VLC was pulled from the iTunes store last time not by evil Sith lord apprentices at Apple, not at the behest of a evil DRM purveyor, nor was it pulled due to threats by the RIAA or MPAA, it was removed at the insistence of a VLC developer

    I believe Joe_Dragon was referring to this recent Slashdot story, where a studio sharing a parent company with an MPAA member submitted a mistaken robo-DMCA notice to Google: HBO Asks Google To Take Down "Infringing" VLC Media Player

  18. Counter-notification by tepples · · Score: 1

    However all Apple sees is an original copyright holder issuing a complaint.

    If the developer who uploaded the app to the App Store believed that the app was properly using the complaining contributor's code under the GNU General Public License, the uploader could have filed a counter-notification. But it turns out that Apple's terms conflict with the Installation Information requirement of the GPL.

  19. Shortcoming my behind by tepples · · Score: 1

    You claim that explicitly preserving users' ability to modify the software (or to hire someone to modify the software) and make use of this modification is a "shortcoming". How so?

  20. The .o files by tepples · · Score: 1

    The impression I got last time I read the LGPL was that static linking was fine as long as you provide the source code and Installation Information for the copylefted parts and the object code (.o files) for everything else. The problem here is that iOS provisioning gets in the way of providing Installation Information.

  21. why not android? by perryizgr8 · · Score: 1

    to hell with ios. they should make vlc for android and watch it become the most
    downloaded app on the play store. i don't think play store will have a problem with
    the gpl.

    --
    Wealth is the gift that keeps on giving.
    1. Re:why not android? by Anonymous Coward · · Score: 1
    2. Re:why not android? by BasilBrush · · Score: 1

      "This is the 14th beta of VLC for Android."

      How appropriate for an app on a Google platform.

  22. Apple store incompatible with free people by Arker · · Score: 3, Insightful

    Here's the thing: for most of us, if the only way to assert our rights involves hiring attorneys for what could easily be a protracted court case, then we have been effectively stripped of our rights.

    Apple's contract, on its face, clearly and plainly requires us to agree to onerous conditions which, on their face, render Apple incapable of qualifying for the GPL. Apple has absolutely zero interest in changing that in any way and has made that very clear. That is their right.

    Using GPL software to entice people into their "system," however, is not their right. Not morally, and not legally. It's a privilege extended only to those willing to comply with the incredibly reasonable, and extraordinarily specific, terms of the GPL. Given that Apple has made it clear they have no interest or intention whatsoever of allowing their customers the essential freedoms the GPL was built to preserve, why on earth would anyone expect them to be allowed to use the code?

    Come on.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  23. Re-signing by tepples · · Score: 1

    Android also uses signed binaries, but anyone who modifies the software can re-sign it with a self-signed certificate and adb install it on a device. The difference with iOS is that a developer doesn't own his own Installation Information.

  24. Having to first replace your PC by tepples · · Score: 1

    You can develop applications for GNU/Linux or Windows using the standard PC you already have or the standard PC that someone else in your household already has. You don't have to first replace your existing PC with a new Mac.

  25. Not Available In U.S. ITunes Store by MBC1977 · · Score: 1

    Well gee thanks, that's plumb useless...seriously. But congratulations to all of the other ITunes users (outside of the US) that can get it.

    --
    Regards,

    MBC1977,
  26. Market share by tepples · · Score: 1

    That would be accurate if Apple had more than 50 percent market share. But a personal computer randomly selected from among the installed base is more likely to be not a Mac than to be a Mac.

    1. Re:Market share by BasilBrush · · Score: 1

      Who's selecting randomly?

      If anyone feels blocked from developing iOS software by the fact that they don't already have a Mac and can't afford one, then I'm happy. That person isn't a serious developer, and will only end up adding crap to the app store.

  27. You are a member of a niche by tepples · · Score: 1

    You are a member of a 7.18% niche (source: Desktop OS Market Share as of June 2013, Net Applications). The majority have standard PCs.

  28. Becoming serious; duplication by tepples · · Score: 1

    For one thing, how should somebody who wants to take advantage of the rights offered in a free software license obtain the capital to become a serious developer? For another, if one serious developer uploads a program to the App Store and distributes the source code to the public, and another serious developer uploads a noticeably improved version of the same program to the App Store, I was under the impression that Apple would still reject the second version as a duplicate.

  29. Windows and Linux by CHIT2ME · · Score: 1

    Windows and Linux have no problem with VLC. Also, neither does Android! VLC doesn't need Apple. I say, stop providing any software under a gnu license to Apple. If their software such as Quick time is so great, make them use that exclusively. They are the walled garden, aren't they? If they want to open the gate to their garden, then, great! Until such time, all this great software should be available only to open operating systems. Yeah, Yeah, I know all you Apple fanboys out there are thinking daggers at me, but, one question; Do you have to pay cash for any of these gnu licensed products obtained thru the App Store? If not, is Apple providing any money to the open-source developers who make this great software possible? I doubt it!!!

    --
    My karma is bad. Don't get too close!!!