LICENSE update; option (c).

Mon, 20 Apr 2020 13:19:58 -0500

author
Tuomo Valkonen <tuomov@iki.fi>
date
Mon, 20 Apr 2020 13:19:58 -0500
changeset 40
927d738d4ca4
parent 39
12fdf0942842
child 41
379c4fbd23ff

LICENSE update; option (c).

LICENSE file | annotate | diff | comparison | revisions
--- a/LICENSE	Mon Apr 20 12:42:24 2020 -0500
+++ b/LICENSE	Mon Apr 20 13:19:58 2020 -0500
@@ -1,8 +1,7 @@
-This software is distributed under an ANTI-ABUSE LICENSE (aka. *f..k
-copyright and f..k distributions license*), and without any warranty
-whatsoever. If you redistribute this software as part of a larger
-collection/distribution/suite of software, you must do either of the
-following:
+This software is distributed under an ANTI-ABUSE LICENSE (aka. *bollocks
+to copyright and distributions* license), and without any warranty whatsoever.
+If you redistribute this software as part of a larger collection, distribution,
+or suite of software, you must do one of the following:
 
 (a) Always redistribute the **unmodified** and **latest** version provided
 by the lead author. If the lead author releases a new version (on a specific
@@ -12,9 +11,11 @@
 (b) Rename the software, and make it obvious that your modified or obsolete
 software is in no way connected to the lead author of the original software.
 The users of your version should under no circumstances be under the
-illusion hat they can contact the lead author or any of the authors of the
+illusion that they can contact the lead author or any of the authors of the
 original software if they have any complaints or queries.
 
+(c) Do not in any way directly expose this software to your users. 
+
 Otherwise, do whatever you want with this software. In particular, you may
 freely use code snippets in other projects.
 

mercurial