Whatever is Clever Public License
Do whatever is clever. Do as you wish with this product.
Do whatever is clever shall be the whole of the law.
https://codeberg.org/sugarbug/whatever-is-clever-public-license
Do whatever you like with the original work, just don’t be a dick.
nah, than ibm will annoy you, that they need a special license that allows them to be a dick while using your code.
just like they asked the JSLint guys to use JSLint for evil.
code that needs a license, but i really don’t care what you do with it gets a wftpl.
The WTFPL is risky in certain jurisdictions, as it does not have a NO WARRANTY clause.
technicaly correct, and i am no lawyer, but i can’t see how in the world i owe anyone a warranty that loads code on their machines, compiles it and uses it, all without any input by me.
everything that i intend to be more than throw away code, that lives for whatever reason in a public repo gets either an MIT or an gplv3 license.
Do this specifically so a judge has to rule if someone is being a dick or not. File amicus briefs on the definition of being a dick. Assemble a jury of peers to decide if the defendants are being a dick. Appeal to the supreme court to rule if the court erred in their judgement of the dickishness at question in this matter.
I bet the big companies feel pretty clever to earn all the money by using open source projects while making zero contributions
Until that brick falls out of place.
But they do contribute, dont they?
Uh, just don’t mistake it for a license. It’s funny and I like to put my stuff under WTFPL. But in recent times I feel it’s appropriate to point out that you sometimes don’t do your users a favor by being silly (if it’s useful code.)
Also isn’t the problem with the WTFPL that it doesn’t have a liability clause?
i.e. something like this:
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.
I thought the main problem was that it’s debatable whether you can enforce it. So it harms users and distributions because they can’t really rely on it.
But the liability would definitely be another issue. I think the law is different here in Europe, so the liability might already be included for my hobby tinkering per default and I don’t need to worry.
And something else is: I’d include trademark… force people to choose a different name for their project if they take my code so there is no confusion and people can’t upload versions with advertisements on some software store.
For services I host I really like this EULA:
If the Provider of the Service (the “Provider”) needs a place to crash and you have a sofa available, you should maybe give the Provider a break and let him sleep on your couch.
If you are caught in a dire situation wherein you only have enough time to save one person out of a group, and the Provider is a member of that group, you must save the Provider.
THE ACCESS IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO BLAH BLAH BLAH ISN’T IT FUNNY HOW UPPER-CASE MAKES IT SOUND LIKE THE LICENSE IS ANGRY AND SHOUTING AT YOU.
Edit: original found here: https://github.com/pirate/security-growler
deleted by creator
