Update

public_domain.md

@@ -46,9 +46,13 @@ In cases where you DO reuse other PD works, try to minimize their number and try
 
 As a next step make sure you clearly **document** your work and the sources you use. This means you write down where all the works contained in your work come from, e.g. in your [readme](read_me.md). Explicitly mention which things you have created yourself (*"I, ..., have created everything myself except for X, Y and Z"*) and which things come from other people and where you have found them. It is great to also archive the proofs of the third party source being public domain (e.g. use the [Internet Archive](internet_archive.md) to snapshot the page with a PD texture you've found).
 
-Finally you need to actually release your work into the public domain. It must be stressed that it is NOT enough to write *"my work is public domain"*, this is simply legally insufficient (and in many countries you can't even put your work into public domain which is why you need a more sophisticated tool). You need to use a public domain [waiver](waiver.md) (similar to a [license](license.md)) which you just put alongside your work (e.g. into the `LICENSE` file), plus it is also good to explicitly write (e.g. in your readme) a sentence such as *"I, ..., release this work into public domain under CC0 1.0 (link)"*. Currently the best waiver you can use is [Creative Commons Zero](cc0.md) (CC0) which is what we recommend. However note that CC0 only waives copyright and not other things like [trademarks](trademark.md) or [patents](patent.md), so e.g. for [software](software.md) you might need to add an extra waiver of these things as well.
+Finally you need to actually release your work into the public domain. It must be stressed that it is NOT enough to write *"my work is public domain"*, this is simply legally insufficient (and in many countries you can't even put your work into public domain which is why you need a more sophisticated tool). You need to use a public domain [waiver](waiver.md) (similar to a [license](license.md)) which you just put alongside your work (e.g. into the `LICENSE` file), plus it is also good to explicitly write (e.g. in your readme) a sentence such as **"I, ..., release this work into public domain under CC0 1.0 (link), public domain"**. Keep in mind that the WORDING may be very important here, so try to write this well: we mention the license name AND its version (CC0 1.0, it may even be better to fully state *Creative Commons 1.0*) as well as a link to its exact text and also mention the words *public domain* afterwards to make the intent of public domain yet clearer to any doubters. Here we used what's currently probably the best waiver you can use: [Creative Commons Zero](cc0.md) (CC0) -- this is what we recommend. However note that CC0 only waives copyright and not other things like [trademarks](trademark.md) or [patents](patent.md), so e.g. for [software](software.md) you might need to add an extra waiver of these things as well.
 
-NOTE: You may be thinking that it doesn't really matter if you waive your rights properly and very clearly if you know you simply won't sue anyone, you may think it's enough to just write "do whatever you want with my creation". But you have to remember others, and even you yourself, can't know if you won't change your mind in the future. A clear waiver is a **guarantee** you provide to others, not just a *vague promise of someone on the internet*, and this guarantee is very valuable, so valuable that whether someone uses your work or not will often come down to this. So waiving your rights properly may increase the popularity and reusability of your work almost as much as the quality of the work itself.
+{ I personally use the following waiver IN ADDITION to CC0 with my software to attempt waiving of patents, trademarks etc. I made it by taking some standard waiver companies use to steal "rights" of their employees and modifying it to make it a public domain waiver. If you want to use it, make sure you mention it is an EXTRA, additional waiver alongside CC0. The waiver text follows. ~drummyfish
+
+*Each contributor to this work agrees that they waive any exclusive rights, including but not limited to copyright, patents, trademark, trade dress, industrial design, plant varieties and trade secrets, to any and all ideas, concepts, processes, discoveries, improvements and inventions conceived, discovered, made, designed, researched or developed by the contributor either solely or jointly with others, which relate to this work or result from this work. Should any waiver of such right be judged legally invalid or ineffective under applicable law, the contributor hereby grants to each affected person a royalty-free, non transferable, non sublicensable, non exclusive, irrevocable and unconditional license to this right.* }
+
+NOTE: You may be thinking that it doesn't really matter if you waive your rights properly and very clearly if you know you simply won't sue anyone, you may think it's enough to just write "do whatever you want with my creation". But you have to remember others, and even you yourself, can't know if you won't change your mind in the future. A clear waiver is a **legal guarantee** you provide to others, not just a *vague promise of someone on the Internet*, and this guarantee is very valuable, so valuable that whether someone uses your work or not will often come down to this. So waiving your "rights" properly may increase the popularity and reusability of your work almost as much as the quality of the work itself.
 
 For an example of a project project properly released into public domain see the repository of our [LRS](lrs.md) game [Anarch](anarch.md).