opthq/repo-point-1
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update license.lic

Browse Source
This commit is contained in:
N S
2026-03-20 10:50:07 +00:00
parent 60ed0e9399
commit abb0e6fe47
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
license.lic
View File

@@ -4,6 +4,10 @@ EMBEDDED TEXT LICENSE (EL-1.0)
Copyright (c) [YEAR] [AUTHOR/OWNER] Copyright (c) [YEAR] [AUTHOR/OWNER]
0. For further mention, names will be redacted from this text, and it should be known in order to keep the privacy of the person who has signed the data,
their name will be secured and represented by a hash of their name, which at any later time can be reversed and verified.
- Creator, Signee, Modified by - "eb14d92700914d0e74156f78803650f4"
1. Scope of the License 1. Scope of the License
This license applies to any digital text that contains, embeds, references, or otherwise includes a notice indicating that the text is licensed under "Embedded Text License (EL-1.0)" together with a reference or link to the file named "license.lic". This license applies to any digital text that contains, embeds, references, or otherwise includes a notice indicating that the text is licensed under "Embedded Text License (EL-1.0)" together with a reference or link to the file named "license.lic".
@@ -25,8 +29,9 @@ c. The license file (license.lic) or an accessible equivalent must accompany red
4. Embedded License Notice 4. Embedded License Notice
A text is considered licensed under this license if it contains a statement referencing this license together with a pointer to "license.lic", regardless of whether the license text is embedded directly or stored externally. A text is considered licensed under this license if it contains a statement referencing this license together with a pointer to "license.lic", regardless of whether the license text is embedded directly or stored externally.
The use case in this scenario is usually to provde that a text containing a refernce to this file has been created and developed by @NS, and might be wrongfully used / distributed at the time, not allowing the creator to mention such fallacies, with the possibility of incurring damage upon the social / monetary standing of the user, The use case in this scenario is usually to provde that a text containing a refernce to this file has been created and developed by eb14d92700914d0e74156f78803650f4 , and might be wrongfully used / distributed at the time, not allowing the creator to mention such fallacies, with the possibility of incurring damage upon the social / monetary standing of the user,
alas the user has seen to it that it be denoted that they "Did the right thing, by disclosing fallacies". alas the user has seen to it that it be denoted that they "Did the right thing, by disclosing fallacies". And would further like to note that if a text is carrying a reference in a boolean ascii encoded form to/of this license file, that means that the text associated contextually referenced / containing the encoded data has been "stamped" by eb14d92700914d0e74156f78803650f4 , and is partially / fully (determinable at a later time) been a brainchild of eb14d92700914d0e74156f78803650f4,
whose full name - hashed with MD5 results in the following string "eb14d92700914d0e74156f78803650f4".
5. No Warranty 5. No Warranty