Remember when people started using WTFPL because it "sounded good", only to later find out it left them and their users legally liable? This is that but for websites.
Since no-one bothered to answer, the way the license was written did not disclaim any warranty. Sure, US jurisprudence might beg that there is no implied warranty, but most jurisdictions would interpret that as having unlimited warranty. In most places, what-you-pay is not the default to warranty claims, but instead focuses on what are the actual damages to the user. Notably, Australian/NZ and EU (especially Germany and Austria) has extremely strong consumer protection laws which also covers software, and WTFPL didn't even attempt to limit liabilities.
NB: For reference, here's the disclaimer for several popular licenses:
MIT:
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
GPLv3:
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
CC0 (just to drive the point home):
4. Limitations and Disclaimers.
(Subsection a (which focused on trademarks and patents) omitted for brevity.)
b. Affirmer offers the Work as-is and makes no representations or warranties of any kind concerning the Work, express, implied, statutory or otherwise, including without limitation warranties of title, merchantability, fitness for a particular purpose, non infringement, or the absence of latent or other defects, accuracy, or the present or absence of errors, whether or not discoverable, all to the greatest extent permissible under applicable law.
I like how, even when the whole point is to not have any terms or conditions, there are still disclaimers. "Only for lawful purposes," "no warranty," "we are not responsible."
Right? Why include that? The law automatically applies. Including it in the license is just redundant.
Had it simply read "You may use this site for any purpose." or "You may use this site." or "You may use this" or "This can be used." it would have the same level actual restriciton in that you obviously aren't allowed to use it to break the law regardless of what it actually says.
And, having typed all that, I realize that there is another restriction in that it presumes that there is a 'you' using it. Things that are not 'you' cannot use it given that it specifically lists 'you' in the referenced parties. "This can be used" would be more permissive.
Probably because the "default" (in the USA and all European states I've checked at least) is copyright protection - unless explicitly stated otherwise the original author has exclusive rights to reproduce or distribute the work.
That means that things with "no license" don't actually mean "you can do whatever you want" - but in fact "you can do realistically nothing".
So to actually let other people so much as look at it, you have to have some kind of license attached already. And then it can be easy to imply (in the eyes of the law) things like "fitness for purpose" or some kind of warrenty unless expicitly denied.
Honestly it's really annoying to find things like code on the internet with "no license" - that just means you can pretty much never even look at it. You could argue that isn't the "right" default, but the law is what the law is right now.
When it's in the contract, then it means that when you break the law you both break the law and the contract. SHould it be necessary? Perhaps not, but in some places that makes a meaningful difference.
This is the real salient point in this post in my opinion;
It unintentionally demonstrates the limits of individual agency to avoid legal embroilments
That is to say: it doesn’t really matter what this person puts on their website because there is a judge and a sheriff somewhere that can force you to do something that would violate the things you wrote down because the things you wrote are subordinate to jurisdictional law (which is invoked as you point out)
It’s actually pretty poetic when you think about it because the page effectively says nothing because it doesn’t have content that the license applies to
If it’s a art piece intended to show something about licensure all it does is demonstrate the degree to which licensure is predicated on jurisdiction
This does not read like it was written by a professional. Non-professionals writing licenses and T&Cs cause problems because no organization, for profit or not, wants to be dragged into court to get a "common sense" definition of a word or comma defined, at their expense.
I've heard of large organizations reaching out to places who use amateur T&Cs and licenses, saying "if we give you $X, can you dual license this as MIT, Apache, BSD, or hell anything standard?".
> Access is not conditioned on approval
Is this obvious enough legalese to not waste tens of thousands of dollars in legal fees if you get sued?
Note before you reply: I will not argue with you about how obvious it is. If you are actually a lawyer then it'd be interesting to hear your guidance, which I very much understand is not legal advice. If you're not a lawyer then I'm not.
I know this is mostly parody, but I'm curious if anyone has good starter templates for something that covers the general stuff and doesn't require a lawyer to customize
"Often one generation values things much more than others. Boomers and their wristwatches. One generation is like 'only from my cold dead hands,' the others 'what would I even need this for?!' What are examples of things the youngest generation did away with?"
If OP were a checklist, the answer would have checked every point.
130 comments
NB: For reference, here's the disclaimer for several popular licenses:
MIT:
GPLv3: CC0 (just to drive the point home):Those are still terms and conditions!
Had it simply read "You may use this site for any purpose." or "You may use this site." or "You may use this" or "This can be used." it would have the same level actual restriciton in that you obviously aren't allowed to use it to break the law regardless of what it actually says.
And, having typed all that, I realize that there is another restriction in that it presumes that there is a 'you' using it. Things that are not 'you' cannot use it given that it specifically lists 'you' in the referenced parties. "This can be used" would be more permissive.
A sure sign of a legal team or possibly an entire legal system having lost the plot. Hopefully only the former.
That means that things with "no license" don't actually mean "you can do whatever you want" - but in fact "you can do realistically nothing".
So to actually let other people so much as look at it, you have to have some kind of license attached already. And then it can be easy to imply (in the eyes of the law) things like "fitness for purpose" or some kind of warrenty unless expicitly denied.
Honestly it's really annoying to find things like code on the internet with "no license" - that just means you can pretty much never even look at it. You could argue that isn't the "right" default, but the law is what the law is right now.
> Right? Why include that? The law automatically applies. Including it in the license is just redundant.
Perhaps not. The law, as automatically applied, often include implied warranties.
It should be called bare-termsandconditions or minimal-termsandconditions.
It unintentionally demonstrates the limits of individual agency to avoid legal embroilments
That is to say: it doesn’t really matter what this person puts on their website because there is a judge and a sheriff somewhere that can force you to do something that would violate the things you wrote down because the things you wrote are subordinate to jurisdictional law (which is invoked as you point out)
It’s actually pretty poetic when you think about it because the page effectively says nothing because it doesn’t have content that the license applies to
If it’s a art piece intended to show something about licensure all it does is demonstrate the degree to which licensure is predicated on jurisdiction
> By accessing or using this site, you acknowledge and accept the following terms.
I’m pretty sure this is already questionable in the EU.
I've heard of large organizations reaching out to places who use amateur T&Cs and licenses, saying "if we give you $X, can you dual license this as MIT, Apache, BSD, or hell anything standard?".
> Access is not conditioned on approval
Is this obvious enough legalese to not waste tens of thousands of dollars in legal fees if you get sued?
Note before you reply: I will not argue with you about how obvious it is. If you are actually a lawyer then it'd be interesting to hear your guidance, which I very much understand is not legal advice. If you're not a lawyer then I'm not.
> Access is not conditioned on approval.
The Zen Koan of T&C's.
that this site definitely
does not, legally
"Often one generation values things much more than others. Boomers and their wristwatches. One generation is like 'only from my cold dead hands,' the others 'what would I even need this for?!' What are examples of things the youngest generation did away with?"
If OP were a checklist, the answer would have checked every point.