>I really don’t care about credit or leaving behind a legacy or such things.
Then use a different license. In 1-clause BSD and Boost licenses the requirement of preserving copyright notices applies only to source code, while 0BSD and CC0 don't require that at all.
Also MIT-0. Note that CC0 is not an OSI-approved license. It was withdrawn because the OSI didn't like that it explicitly does not grant patent rights to use the software.
When I read your comment I initially thought "that can't be right".
And then I found [1]:
> CC0 was not explicitly rejected, but the License Review Committee was unable to reach consensus that it should be approved, and Creative Commons eventually withdrew the application. The most serious of the concerns raised had to do with the effects of clause 4(a), which reads: "No ... patent rights held by Affirmer are waived, abandoned, surrendered, licensed or otherwise affected by this document.". While many open source licenses simply do not mention patents, it is exceedingly rare for open source licenses to explicitly disclaim any conveyance of patent rights, and the Committee felt that approving such a license would set a dangerous precedent, and possibly even weaken patent infringement defenses available to users of software released under CC0.
For the record, the FSF also recommends against using CC0 for software for the exact same reason [2].
I was surprised because my first impression was that this clause does not legally do anything more, anything less than a license that does not explicitly grants the rights to use the related software patents anyway. But I can imagine that without an explicit mention, a judge could still decide that a user receiving a program could reasonably feel allowed to use the related patents from its authors.
Anyway, CC0 should not be used or software indeed I guess, given the vagueness around it.
>I was surprised because my first impression was that this clause does not legally do anything more, anything less than a license that does not explicitly grants the rights to use the related software patents anyway. But I can imagine that without an explicit mention, a judge could still decide that a user receiving a program could reasonably feel allowed to use the related patents from its authors.
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
Version 2, December 2004
Copyright (C) 2004 Your Name <name@example.com>
Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.
DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. You just DO WHAT THE FUCK YOU WANT TO.
That license doesn't seem to satisfy the parent's requirements:
> gets me out of any legal responsibility/liability
The license you posted doesn't disclaim any warranties or liabilities. I suggest reading what TFA's "Warranty Disclaimer" section says about UCC defaults. The way I read it (IANAL), you would have more liability with the license you posted than you would under the MIT license.
Then use a different license. In 1-clause BSD and Boost licenses the requirement of preserving copyright notices applies only to source code, while 0BSD and CC0 don't require that at all.