5 ms·
This makes absolutely no sense. I'm almost certain that Square lawyers fucked up big time. They looked at the AGPL and completely misunderstood the context. T
by nabla9 7y ago
This makes absolutely no sense. I'm almost certain that Square lawyers fucked up big time.
They looked at the AGPL and completely misunderstood the context. There is no way in hell anyone can interpret AGPL in a way that makes Square responsible for any license violations their customers make selling software.
- bubblethink 7y agoAnd even if there were liability concerns due to copyleft or other clauses in AGPL, singling out AGPL makes no sense. If they want to avoid copyleft, it should be better phrased like so.
- nabla9 7y agoIt's almost like they used some kind of AI software to scan legal documents, then it found sentence fragments like " .. opportunity for all users interacting with your Program through a computer network ..". You need artificial stupidity to misunderstand the "Interacting with Program through a computer network" in the way Square seems to understand it. Distributing software via online store is not interacting with the program.
- Beltiras 7y agoSome would maintain that being a legal analyst requires you to be artificially stupid because you are looking for loopholes and trying to avoid being trapped by ridiculous edge cases, whereas AI is trying to find a general solution that will work in 6-9s cases.
- EdwardDiego 7y ago> Distributing software via online store is not interacting with the program. Has that been tested in a court yet? If it hasn't, then a lawyer would immediately see risk. I mean, look at Oracle vs Google on whether or not an API is copyrighted.
- chmarr 7y agoFrom the very specificity of the restriction, I gather that they're not copyleft-adverse. They're "Don't upload stuff that risks us being forced to divulge our closed-source code.". Without the prohibition, even if a user of the service included some AGPL libraries without Square's knowledge, a cunning lawyer could argue that Square was complicit in distributing this code to end-users and thus liable. The prohibition makes that argument difficult.
- eesmith 7y agoA cunning lawyer could argue anything. But, when did Square ever agree to the copyright license? Who did the actual copyright infringement? And AGPL isn't the only "must publish all your server's source code" license available, so to prohibition is too specific if that's the actual reason.
- MaulingMonkey 7y agoSquare is bound by copyright law just as much as anyone else. Agreeing to that license is the only thing giving them permission to redistribute it in the first place. This is why we have the DMCA safe harbor provisions - it'd be incredibly easy to be on the hook for copyright infringement as a company hosting any user content otherwise. Those safe harbor provisions aren't a blank check to knowingly commit wanton copyright infringement however, as can be seen with all the legal wrangling over Megaupload, as an example [1]. Square knows about the AGPL, knows they might not be abiding by it's terms if they redistribute AGPL code, and knows they probably don't have the right to redistribute under any other term. They can choose to knowingly possibly violate the license, or to knowingly commit copyright infringement, or to ban AGPL code. Those first two options, with that "knowingly" in there, open them up to potential legal action. > And AGPL isn't the only "must publish all your server's source code" license available, so to prohibition is too specific if that's the actual reason. If you make Square's lawyers aware of some of those other licenses, it wouldn't suprise me if they get banned too for the same reason. It's not like they have psychic knowledge of the existence of all licenses. Failure to audit the universe doesn't mean that's not their reason. [1] https://en.wikipedia.org/wiki/Megaupload#Safe_harbor_provisions https://en.wikipedia.org/wiki/Megaupload#Safe_harbor_provisi...
- tzs 7y agoNote: I've not looked into the details of what square is doing. This comment is on AGPL in general compared to other licenses. It does make some sense to see AGPL singled out, because it is different from most other free and open source licenses in one major way. Almost all other free and open source licenses only require you to distribute modified source code of a derivative work you've made if you distribute that derivative work. If I take code under those licenses, modify it, link it with my own code, and just run the resulting derivative work on my computer, they do not require me to distribute those modifications or my code, no matter what I'm using the program for, or where from, who from, or how I get its input, or what I do with, where I send, or who I give its output. Not so with AGPL. With AGPL, the requirement to distribute derivative works can be triggered by code running entirely on my computer if it gets its input from and sends its output to people over a network. That's a huge difference from prior free and open source licenses.
- ralph84 7y agoThis almost certainly is about keeping Square’s code closed source, not anything to do with Square’s customers selling software.
- merb 7y agoI see that aswell. else, google would need to provide the source code for gcloud, since I can run agpl software on top of their compute nodes... like wtf?
- rambojazz 7y agoBTW, isn't this the exact purpose of the new MongoDB license?
- ceejayoz 7y agoNo, not at all. MongoDB's new license targets scenarios where Google would provide a hosted MongoDB service to their customers (like Amazon's RDS offering, for example). It has no impact on individual customers personally spinning up their own MongoDB on their own set of servers for their own use.
- rambojazz 7y agoMy comment was a reply to the parent comment, not a reference to the article. What the parent comment says sounds like the true purpose of the new mongo license.
- giancarlostoro 7y agoI mean I never understood AGPL for client-side code to be honest. Would the GPL not cover this use case? My understanding of the license is that the GPL would of been enough, unless the AGPL has some terms I'm not aware of that aren't server specific like ensuring access to code in unobsfucated form or something.
- zanny 7y agoAGPLv3 is a superset of GPLv3. If you never expect your code to be hosted the GPL is all you need to guarantee user freedoms.
- sokoloff 7y agoI don't think your expectations are the limit, but rather what your users (and their users) will end up actually doing, whether or not you expect or foresee it.
- resoluteteeth 7y agoI think this is about including AGPL code in a website that you have hosted by Square. They are probably worried that if AGPL code is included, this will result in Square sending it to browsers together along with their own proprietary code, which could be interpreted as an AGPL violation by Square. Honestly they are probably correct to be worried about this because it's pretty unclear whether or not it would be covered. At the very least, by making it against the TOS it is clear that it's the users fault not theirs if there is a violation.
- LinuxBender 7y agoWe have the same issue at my workplace. Legal won't let us near anything AGPL in our projects for those reasons.
- mjevans 7y agoI am not a lawyer - However my own take on the AGPL is that if there's an external tool, an entirely separate process that is open source and does things, then as long as that source code is published and public a user is OK to use AGPL things. As an example, let's say that I have a game. That game happens to want to have a way of rendering some HTML content for printing / making a PDF. It's OK to ship an open source thing with your game, like a hypothetical FrozenFluff web-browser licensed in AGPL. There are two distinct entities there: a FF binary that gets called with a file to render (which is AGPL and an AGPL processed result that is under the copyright of whomever's material was rendered) and another distinct binary the GameX that happened to call an external process. The line to cross there is that the AGPL stuff can't be linked against your own program. I'm even more unsure how a module might or might not be licensed. I think since that's an addin then the code for the module (including headers) would have to be AGPL compatible and released, but that the rest could probably be closed. This line is less clear when it comes to websites however. I think the best equivalent would be to make a wrapper interface that is AGPL licensed, published, and links to/calls the AGPL software. It should have a distinct URL. That URL might only be on the localhost (for security) and would hand back whatever results exist. The proprietary interface could talk to that URL and get results.
- ksec 7y agoI just wanted to mention I upvoted you but I disagree with you. And there are enough explanations given below your comment then I can write.