5 ms·
It's ambiguous for several reasons. There's not much preventing me from re-assinging copyright to myself (in countries that allow it) and then suing the origin
by Alupis 12y ago
It's ambiguous for several reasons.
There's not much preventing me from re-assinging copyright to myself (in countries that allow it) and then suing the original creator.
There's nothing to stop me from taking your code, re-licensing it under say a proprietary license, then suing the original creator.
There's nothing that stops me from taking your project's branding/symbol/graphics/name and claiming it as my own and then suing you.
There's nothing that stops me from taking your work and then not providing attribution back to the original creator.
By default there is nothing that absolves the license holder from warranty nor implied fitness for use. (If it destroys my computer running your code, I can sue you, and worse, you accept liability by default). That is, unless you include the optional snippet of text that absolves any warranty issues... but since it's optional, and not on the main license page (it's in the FAQ page), many authors forget to include this.
There are other things too... like, legally, what does "DO WHAT THE FUCK YOU WANT" actually mean? The law is black and white (or at least we try to be), being in the grey opens the door for abuse. Has it been challenged before in a legal sense? Has a lawyer reviewed it?
While I certainly understand the intent and spirit of this license; this license appears to be nothing more than a bad (and somewhat distasteful) joke that serves more harm than good.
I agree, better off choosing a public domain license or one of the several vetted FOSS licensees.
- clarry 12y agoWe discussed this before[1] but you failed to back up any claims about this re-licensing and re-assigning business you vent about here. You still haven't explained how you can take away someone else's rights. Copyright licenses are used to grant other people rights, not to take them away. You still haven't read the Berne convention, have you? Can you point at a case in any country that suggests the license could be interpreted outside the context of copyright? I.e. that "do what the fuck you want" in a copyright license can be seen as granting someone rights beyond the ones (related to copying, modification, performance, etc.) that are normally exclusive to the author and therefore require him to use a license to grant others these same rights? If you can't back anything up, I don't think you should be spreading your own interpretations in this manner, presenting them as truth. We already have far too many people confused over licenses, and passing that confusion on doesn't help anyone. [1] https://news.ycombinator.com/item?id=8043969 https://news.ycombinator.com/item?id=8043969
- Alupis 12y agoPerhaps I missed something... But I don't see where you substantiate any of your claims. You seem to just want to defend an obviously joke license. This license, from my interpretations, forfeits most of the copyright protections, including allowing someone to re-license (per the FAQ of the license). At the end of the day, you are free to use whatever license you think suits you best. That does not mean it actually suits you best. (As demonstrated by Debian putting their foot down on other BS licenses such as this).
- clarry 12y agoRe-licensing remains a horribly confusing term, which is something I complained about. Some people use it to mean substitute the license on your copy with some other license, and then pass copies on under that new license. This appears to be the way the FAQ uses the term. The way you use the term, you seem to think that you can actually do some magic and revoke the author's rights, then impose your conditions on him, and possibly sue him for violating these conditions. That's just bullshit, it doesn't work like that. Unless you know something the rest of the world doesn't. You keep saying copyright licenses are used to "forfeit" (by which I assume you mean surrender) rights, so as to (exclusively) transfer them from you to someone else. It doesn't work like that. They are used to grant other people rights. They normally do not remove any rights from the author. And you still maintain your circular definition of copyright, in which authorhood or copyright itself is a right protected by copyright and that through one of the rights protected by copyright (and granted to you by an author's license), you can obtain that right which is copyright (or authorhood). Can you please back any of it up?
- Alupis 12y agoEven if your argument regarding copyright is valid (I don't believe all of it is valid), this still does nothing to address the other (numerous) issues I've raised with this particular license. Like I said before -- use a more appropriate license that still provides the goals you intend. As a side note -- don't accuse me of not backing up my claims when neither do you... at this point, we're just two guys bickering on a forum.
- jvdh 12y agoCopyright is not something you can take away. It exists from the moment you create something creatively and originally. You can however license someone to use something that is protected by copyright. This is what licenses do; they give you a license to use the content. This is exactly what CC0 tries to do, it works around the fact that you cannot (easily) give away or stop copyright, but can state that you distance yourself from all the rights that come with having the copyright. See also: http://creativecommons.org/about/cc0 http://creativecommons.org/about/cc0
- daxelrod 12y ago> There's not much preventing me from re-assinging copyright to myself (in countries that allow it) and then suing the original creator. In what jurisdictions would that be interpreted as copyright reassignment? I can see how you might argue that "re-assign copyright to myself" is WTF you want to do, but the onus is on the creator to assign copyright to you. > There's nothing to stop me from taking your code, re-licensing it under say a proprietary license, then suing the original creator. Suing them for what? There's nothing to prevent you from suing pretty much anyone, for any reason, including any of the other licenses. Second of all, if you're saying there's nothing preventing your suit from being successful, I still don't understand on what grounds. It doesn't matter what licence you've relicensed under if the original author holds copyright. > There's nothing that stops me from taking your project's branding/symbol/graphics/name and claiming it as my own and then suing you. You could do this no matter what the license. What about the WTFPL would make your lawsuit any more successful than any other licence? > There's nothing that stops me from taking your work and then not providing attribution back to the original creator. This is fully within the intent of the WTFPL. > By default there is nothing that absolves the license holder from warranty nor implied fitness for use. You have a good point that this is something many people would want. Do you know in which jurisdictions this is actually needed? I wasn't able to find any sources for this. > Has it been challenged before in a legal sense? Has a lawyer reviewed it? Excellent points.
- DannyBee 12y agoOkay, lawyer time. Some of these concerns are overblown, some aren't. First, the license grant is clearly ambiguous. Most license grants are written in terms of exclusive rights of copyright (ie reproduction, derivative work creation, public performance). This one isn't. "Do whatever the fuck you want' is unclear as to exactly what rights you can exercise and can't, because "whatever you want" can be found to not literally be "whatever" (and in fact, when most people say "you can do whatever you want", they often mean "whatever you want within reason") Maybe a judge will agree with "it means all of them", maybe they won't. It depends on the situation. I wouldn't want to bet my life on it. Damages would likely be minimal in such a case, except in places with high statutory damages awards. You might get enjoined from using it. Second, As for reassigning copyright, probably not. In most jurisdictions, this requires a specific signed instrument. Third, you can't put it under a new license and sue the creator, they also have rights to it. Fourth, "You have a good point that this is something many people would want. Do you know in which jurisdictions this is actually needed? I wasn't able to find any sources for this." At the very least, in the US it's a very bad idea not to disclaim warranties. Particularly since people are making warranties on mailing lists as to fitness, etc, all the time. I can't stress enough how dangerous it is to not disclaim warranties in the US. > Has it been challenged before in a legal sense? Has a lawyer reviewed it? Excellent points." OSI declined to name it an open source license, considering it mostly duplicative of others. I specifically try to push people to avoid it, and the company i work for won't distribute software that uses it.
- yellowapple 12y ago> There's not much preventing me from re-assinging copyright to myself (in countries that allow it) and then suing the original creator. By that logic, public domain is "ambiguous". > There's nothing to stop me from taking your code, re-licensing it under say a proprietary license, then suing the original creator. By that logic, virtually all the "BSD-style" licenses and their ilk are "ambiguous". > There's nothing that stops me from taking your project's branding/symbol/graphics/name and claiming it as my own and then suing you. By that logic, virtually every FOSS license that doesn't extend to branding (e.g. pretty much everything other than the MPL) is "ambiguous". > There's nothing that stops me from taking your work and then not providing attribution back to the original creator. See the public domain remark above. > By default there is nothing that absolves the license holder from warranty nor implied fitness for use. That is true, and would be a worthwhile addition as a default rather than an afterthought. > legally, what does "DO WHAT THE FUCK YOU WANT" actually mean? It means "do what you want". Unless you're claiming that lawyers don't have a strong-enough grasp of the English language to be able to properly interpret extraneous expletives (which wouldn't surprise me to be quite honest...).
- Yver 12y ago> By that logic, public domain is "ambiguous". The notion of public domain can vary from country to country. The first time I wanted to release something inconsequential on Google Code I was surprised that it didn't let me choose "Public domain" and forced me to choose a license. Here's their FAQ about it: http://code.google.com/p/support/wiki/FAQ#Can_I_host_code_that_I_have_placed_in_the_public_domain http://code.google.com/p/support/wiki/FAQ#Can_I_host_code_th...?
- DannyBee 12y ago"It means "do what you want". Unless you're claiming that lawyers don't have a strong-enough grasp of the English language to be able to properly interpret extraneous expletives (which wouldn't surprise me to be quite honest...)." This is a very simplistic view of the phrasing. For starters, when I ask someone "hey do you mind if i do x", and they say "do whatever you want", it doesn't usually mean "yes it is okay if i stab you with a knife", it means "yes it is okay to do x". This phrase does not have a single, simple definition that is clear and robust.
- Semaphor 12y agoGo on, sue all the people publishing stuff in the public domain. Because surely you can magically re-license it under your own copyright and sue them.