3 ms·
The license to "use, display and perform your Content" isn't limited to the GitHub site or functionality. Only the "access your Content" and "reproduce your Co
by JoshTriplett 10y ago
The license to "use, display and perform your Content" isn't limited to the GitHub site or functionality. Only the "access your Content" and "reproduce your Content" are limited to GitHub.
> The only real problem I see here is that unless you created the work entirely by yourself ("you" here can mean a group), you can't grant the rights necessary to upload to Github, even if you're well intentioned or the original authors may be fine with it. And these rules apply to private repos, too. I wish the author had focused more on that.
The author did explicitly mention that. But I think it's worth listing all the issues with the ToS, not just one.
- E6300 10y ago> The license to "use, display and perform your Content" isn't limited to the GitHub site Right. If you put up your code publicly you are implicitly allowing other people to do those things, since there's nothing you can do to stop it. How could you stop someone from privately running your code on their hardware? You're also implicitly allow people to fork and download the code, since Github doesn't allow public projects to restrict those abilities. Your particular license may restrict making further copies, though.
- JoshTriplett 10y ago> Right. If you put up your code publicly you are implicitly allowing other people to do those things, As one example, "display" isn't made contingent on attribution. As an unusual but plausible example: a GitHub user could grab a pile of code from across GitHub and render it to construct a "movie hacking UI" for a film, without even an attribution for the code they used. > since there's nothing you can do to stop it. How could you stop someone from privately running your code on their hardware? (Also, "nothing you can do to stop it" is not a grant of permission.)
- matthewmacleod 10y agoAs one example, "display" isn't made contingent on attribution. That's fine, but in general these software licenses do not cover "display", they cover _distribution_. If you consider "using code in a movie hacking UI" to be distribution, then you would already have been bound by the license. If you don't, then you're not. Nothing changes.
- dragonwriter 10y ago> That's fine, but in general these software licenses do not cover "display", they cover _distribution_. Yes, that means that "display", insofar as that corresponds to a copyright-protected exclusive right like performance, is not licensed by the license, and (if you aren't the original copyright holder) you have no authority to grant a sublicense to GitHub that covers display.
- E6300 10y ago> Also, "nothing you can do to stop it" is not a grant of permission. Okay, well, I give you permission to copy the words in this sentence into your brain, but you're not allowed to process their semantic content into a coherent idea. If you do, I will sue you.
- Filligree 10y agoSurprisingly, the law is neither completely consistent nor interpreted by a computer. Largely to avoid that sort of thing.
- systoll 10y agoIf the code were kept secret, or if you could prevent such use with DRM, copyright law would be irrelevant. By having the code in the open, you don't 'implicitly allow' unlicensed uses -- you just become reliant on copyright law as your protection.
- squeaky-clean 10y ago> The license to "use, display and perform your Content" isn't limited to the GitHub site or functionality. Only the "access your Content" and "reproduce your Content" are limited to GitHub. Hmmm, I see how the and can be read that way. They really need to use more punctuation in these instead of so many 'and's. But so if they can only access and reproduce your content through Github, what constitutes use/display/perform, and in what ways could they do that? Judging by the way D.4 is written, I take it to mean things like playing an audio file or running some executable code within the browser. > The author did explicitly mention that. But I think it's worth listing all the issues with the ToS, not just one. Yeah, I get that they mentioned it, I meant I wished they spent more than a sentence on it because I feel that's the bigger issue.
- randallsquared 10y ago> But so if they can only access and reproduce your content through Github, what constitutes use/display/perform, and in what ways could they do that? IANAL, nor do I have a dog in this fight, since I prefer contracts to copyrights. However... I think there are at least a few scenarios that require some thinking about, anyway: Given that the TOS forces allowance of use and performance of content uploaded to Github without regard to any license you might have been bound by otherwise, it seems as though it effectively negates any other such restriction. CC BY-NC doesn't allow commercial use, but now they can just point to the implicit license they got with it because you shared it on Github, right? The AGPL requires that modified source used to furnish a direct service must be republished. If usage of Github means that you have granted a license, separately from the AGPL, to every user of Github to use your software, then publishing AGPL software via Github seems to negate the license: anyone who has it and who got it using Github may use it to run a server and need not follow the terms of the AGPL to do so. But this leads to problems with other restrictive licenses as well, such as the GPL, since as long as someone is only distributing your software via Github, they have a license to reproduce it without regard to other terms like modification of source, and other Github users have a license to download and use it.
- belorn 10y agoEven if we see it as a granted license, separately from the AGPL, it would be "solely on GitHub" that people can enjoy those permissions and the permission do not allow making copies that leaves github. This would of course not work if github became in future a hosting service where people could run projects as services on their platform.