Return to Answer

I've covered a number of practical uses for attaching a license like the WTFPL in a response to a similar but more pointed question. Your claim that CC0 is more liberal is incorrect as CC0 comes with a number of limitations the WTFPL doesn't have such as limitations on:

• Patent use;
• Warranty;
• Trademark use; and,
• Liability.

In fact WTFPL has no restrictions whatsoever other than to change the license name if the license is changed. WTFPL is also useful if you plan to dual-license software and don't want to fall into the permissive license attribution landmine, or copyleft just yet. And since there's no “Public Domain” dedication WTFPL may can make sense in jurisdictions where some law isn't recognized just yet.

Can you get sued? Sure. But putting a disclaimer in any license doesn't change the fact anyone may sue you at anytime for any reason. BUT IF YOU WANT YOUR UNCONDITIONAL LICENSE TO SCREAM A LITTLE 0BSD WILL GIVE YOU JUST THAT.

I've covered a few of practical uses for attaching a license like the WTFPL in a response to a similar but more pointed question. The claim CC0 is more liberal is incorrect as CC0 comes with a number of limitations the WTFPL doesn't have such as limitations on:

• Patent use;
• Warranty;
• Trademark use; and,
• Liability.

In fact WTFPL has no restrictions whatsoever other than to change the license name if the license is changed. It's is also useful if you plan to dual-license software and don't want to fall into the permissive license attribution landmine, or copyleft just yet. And since there's no “Public Domain” dedication WTFPL may can make sense in jurisdictions where some law isn't recognized just yet.

Can you get sued? Sure. But putting a disclaimer in any license doesn't change the fact anyone may sue you at anytime for any reason. BUT IF YOU WANT YOUR UNCONDITIONAL LICENSE TO SCREAM A LITTLE 0BSD WILL GIVE YOU JUST THAT. PRACTICALLY SPEAKING.

I've covered a number of practical uses for attaching a license like the WTFPL in a response to a similar but more pointed question. Your claim that CC0 is more liberal is incorrect as CC0 comes with a number of limitations the WTFPL doesn't have such as limitations on:

• Patent use;
• Warranty;
• Trademark use; and,
• Liability.

In fact, WTFPL has no limitations whatsoever other than to change the license name if the license is changed. Because WTFPL does not include a “Public Domain” dedication it may be used more freely in jurisdictions where such a concept is unrealized. It's also useful if you're planning potentially dual-license your software in that some may not be comfortable with the License name as-is and would be willing to pay to change it.

Can you get sued? Sure. Putting a disclaimer in any license doesn't change the fact anyone may sue you at anytime for any reason, however frivolous, because that's how the law typically works.

I've covered a number of practical uses for attaching a license like the WTFPL in a response to a similar but more pointed question. Your claim that CC0 is more liberal is incorrect as CC0 comes with a number of limitations the WTFPL doesn't have such as limitations on:

• Patent use;
• Warranty;
• Trademark use; and,
• Liability.

In fact WTFPL has no restrictions whatsoever other than to change the license name if the license is changed. WTFPL is also useful if you plan to dual-license software and don't want to fall into the permissive license attribution landmine, or copyleft just yet. And since there's no “Public Domain” dedication WTFPL may can make sense in jurisdictions where some law isn't recognized just yet.

Can you get sued? Sure. But putting a disclaimer in any license doesn't change the fact anyone may sue you at anytime for any reason. BUT IF YOU WANT YOUR UNCONDITIONAL LICENSE TO SCREAM A LITTLE 0BSD WILL GIVE YOU JUST THAT.

I've covered a number of practical uses for attaching a license like the WTFPL in a response to a similar but more pointed question. Your claim that CC0 is more liberal is incorrect as CC0 comes with a number of limitations the WTFPL doesn't have such as limitations on:

• Patent use;
• Warranty;
• Trademark use; and,
• Liability.

In fact, WTFPL has no limitations whatsoever. And because WTFPL does not include a “Public Domain” dedication it may be used more freely in jurisictions where such a concept is unrealized. It's really that liberal.

Can you get sued? Sure. Though putting a disclaimer in any license doesn't change the fact anyone may sue you at anytime for any reason, however frivolous, despite what you may think.

I've covered a number of practical uses for attaching a license like the WTFPL in a response to a similar but more pointed question. Your claim that CC0 is more liberal is incorrect as CC0 comes with a number of limitations the WTFPL doesn't have such as limitations on:

• Patent use;
• Warranty;
• Trademark use; and,
• Liability.

In fact, WTFPL has no limitations whatsoever other than to change the license name if the license is changed. Because WTFPL does not include a “Public Domain” dedication it may be used more freely in jurisdictions where such a concept is unrealized. It's also useful if you're planning potentially dual-license your software in that some may not be comfortable with the License name as-is and would be willing to pay to change it.

Can you get sued? Sure. Putting a disclaimer in any license doesn't change the fact anyone may sue you at anytime for any reason, however frivolous, because that's how the law typically works.