From 13b5ed9044b6e62680d25fd7d4458585a1b7ea81 Mon Sep 17 00:00:00 2001 From: PeacefulPotato <57071692+PeacefulPotato@users.noreply.github.com> Date: Fri, 4 Dec 2020 15:09:30 -0500 Subject: [PATCH 1/9] Create pull_request.md --- .github/PULL_REQUEST_TEMPLATE/pull_request.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 .github/PULL_REQUEST_TEMPLATE/pull_request.md diff --git a/.github/PULL_REQUEST_TEMPLATE/pull_request.md b/.github/PULL_REQUEST_TEMPLATE/pull_request.md new file mode 100644 index 0000000..1fc461e --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE/pull_request.md @@ -0,0 +1,7 @@ + +**Changes** +A bulleted list of the changes you made. Will be used in release notes. +**Reasoning** +Why you want to make these changes. Should be clear and concise. +**Drawback Handling** +Potential drawbacks in this change and how you addressed them. -- 2.38.5 From e8eafd2cee898b9bf06845bc4e5361e9ef1beadb Mon Sep 17 00:00:00 2001 From: PeacefulPotato <57071692+PeacefulPotato@users.noreply.github.com> Date: Fri, 4 Dec 2020 15:11:48 -0500 Subject: [PATCH 2/9] Update CONTRIBUTING.md --- CONTRIBUTING.md | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d87c4a9..0fe7e28 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,5 +1,5 @@ # Issues -There are three types of issues: Bugs, Questions and Enhcanements. +There are three types of issues: Bugs, Questions and Enhcanements. For all issues, make sure you aren't posting a duplicate. ## Bugs Bugs are things that are supposed to work but don't. Some examples include: @@ -14,22 +14,14 @@ Non examples include: If you find a bug, label it with the "bugs" tag, as well as the "security" tag if the bug relates to security. Then, be sure to label it based on the bug report template. ## Questions -Questions are things that you are unsure about. When in doubt, mark it as a question. If you have a question, label it based on the question template. +Questions are things that you are unsure about. When in doubt, mark it as a question, though be sure to always answer it yourself before posting. Be sure to format the enhancement as dicated in the feature request template, though be sure to always answer it yourself before posting. ## Enhancements -Enhancements are things you want to improve. Be sure to list it both as an enhancement and label it based on what type of enhancement it is: +Enhancements are things you want to improve. Be sure to label it based on what type of enhancement it is: Security: This is an improvement to security you would like to see, such as RSA encryption. QOL: This is an improvement to quality of life you would like to see, such as more lanugages as codes. If in doubt, mark it as QOL. Documentation: This is an improvement to documentation you would like to see. -Be sure to label the enhancement based on the feature request template. +Be sure to format the enhancement as dicated in the feature request template. # Pull Requests Pull requests are when you want to change the code yourself. Please link to any relavent issues by clicking on the gear next to "linked issues". Additionally, add this to the milestone the issues are linked to, and label it based on what you are trying to solve (Bug or Enhancement and what type if necessary). -They should be formatted as follows: -``` -**Changes** -A bulleted list of the changes you made. Will be used in release notes. -**Reasoning** -Why you want to make these changes. Should be clear and concise. -**Drawback Handling** -Potential drawbacks in this change and how you addressed them. -``` +They should be formatted as dictated in the pull request template. -- 2.38.5 From b624f8c39b2e452594e370796d9633918d475ba2 Mon Sep 17 00:00:00 2001 From: PeacefulPotato <8162759-PeacefulPotato@users.noreply.gitlab.com> Date: Tue, 9 Feb 2021 19:04:55 +0000 Subject: [PATCH 3/9] Fix typos --- CONTRIBUTING.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0fe7e28..c9f575f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,5 +1,5 @@ # Issues -There are three types of issues: Bugs, Questions and Enhcanements. For all issues, make sure you aren't posting a duplicate. +There are three types of issues: Bugs, Questions and Enhancements. For all issues, make sure you aren't posting a duplicate. ## Bugs Bugs are things that are supposed to work but don't. Some examples include: @@ -14,13 +14,13 @@ Non examples include: If you find a bug, label it with the "bugs" tag, as well as the "security" tag if the bug relates to security. Then, be sure to label it based on the bug report template. ## Questions -Questions are things that you are unsure about. When in doubt, mark it as a question, though be sure to always answer it yourself before posting. Be sure to format the enhancement as dicated in the feature request template, though be sure to always answer it yourself before posting. +Questions are things that you are unsure about. When in doubt, mark it as a question, though be sure to always answer it yourself before posting. Be sure to format the enhancement as dictated in the feature request template. ## Enhancements Enhancements are things you want to improve. Be sure to label it based on what type of enhancement it is: Security: This is an improvement to security you would like to see, such as RSA encryption. QOL: This is an improvement to quality of life you would like to see, such as more lanugages as codes. If in doubt, mark it as QOL. Documentation: This is an improvement to documentation you would like to see. -Be sure to format the enhancement as dicated in the feature request template. +Be sure to format the enhancement as dictated in the feature request template. # Pull Requests Pull requests are when you want to change the code yourself. Please link to any relavent issues by clicking on the gear next to "linked issues". Additionally, add this to the milestone the issues are linked to, and label it based on what you are trying to solve (Bug or Enhancement and what type if necessary). -- 2.38.5 From e17d209ece65fda80df90481bb122675051991f2 Mon Sep 17 00:00:00 2001 From: PeacefulPotato <8162759-PeacefulPotato@users.noreply.gitlab.com> Date: Tue, 9 Feb 2021 19:07:53 +0000 Subject: [PATCH 4/9] Update to 1.0.2.1: Clarify more apps that the markdown optimization feature supports --- HOP 1.0.2.py => HOP 1.0.2.1.py | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) rename HOP 1.0.2.py => HOP 1.0.2.1.py (94%) diff --git a/HOP 1.0.2.py b/HOP 1.0.2.1.py similarity index 94% rename from HOP 1.0.2.py rename to HOP 1.0.2.1.py index 651e0fc..6fc1582 100644 --- a/HOP 1.0.2.py +++ b/HOP 1.0.2.1.py @@ -19,6 +19,8 @@ #Added several files, including .replit, CODE_OF_CONDUCT.md, CONTRIBUTING.md, README.md, and SECURITY.md #Moved input, print, and import statements outside functions #Added ability to choose on runtime encode or decode + #1.0.2.1: + #Made changes to show that the "optimize for Discord" option also supports Element/Matrix, IRC, Joplin, etc. import base64 def decode(ciphertext, key): @@ -141,11 +143,11 @@ def encode(plaintext, key): stepfour = str(stepthreeb)+"h" answer = False while answer == False: - discord = input("Optimize for discord? y or n: ") - if(discord=="y"): + mdsupport = input("Optimize for markdown supported services, like Discord, Element/Matrix, Joplin, or IRC? y or n: ") + if(mdsupport=="y"): answer = True stepfour = "```"+str(stepthreeb)+"h```" - elif(discord=="n"): + elif(mdsupport=="n"): answer = True output="Your encoded message: "+stepfour return output -- 2.38.5 From ecd72264333c1df8b918ac06b361304e9dcc8abd Mon Sep 17 00:00:00 2001 From: ziproot Date: Mon, 25 Oct 2021 02:35:31 +0000 Subject: [PATCH 5/9] Remove Code of Conduct --- CODE_OF_CONDUCT.md | 56 ---------------------------------------------- 1 file changed, 56 deletions(-) delete mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md deleted file mode 100644 index 2f272cf..0000000 --- a/CODE_OF_CONDUCT.md +++ /dev/null @@ -1,56 +0,0 @@ -# Contributor Covenant Code of Conduct - -## Our Pledge - -In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a -harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, -education, socio-economic status, nationality, personal appearance, race, religion, political party, or sexual identity and orientation. - -## Our Standards - -Examples of behavior that contributes to creating a positive environment include: - -* Using welcoming and inclusive language. For instance, try using "they", "them", etc. whenever possible. -* Being respectful of differing viewpoints and experiences. -* Gracefully accepting constructive criticism, and giving constructive criticism gracefully. -* Focusing on what is best for the community. -* Showing empathy towards other community members. - -Examples of unacceptable behavior by participants include: - -* Anything NSFW. This is a github page for an obsfucation program. -* Trolling, insulting/derogatory comments, and personal or political attacks. -* Public or private harassment. -* Publishing others' private information, such as a physical or electronic address, without explicit permission. -* Other conduct which could reasonably be considered inappropriate in a professional setting. AKA, just because it isn't explicitly stated here doesn't mean you get to do it. - -## Our Responsibilities - -Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any -instances of unacceptable behavior. - -Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned -to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. - -## Scope - -This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a -project or community include using an official project e-mail address (the email address given is not an official email address), posting via an official social media account, -or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. - -## Enforcement - -Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting me at my Discord: PeacefulPotato#4024. All complaints will be reviewed and -investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality -with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. - -Project maintainers who do not follow or enforce the Code of Conduct in good -faith may face temporary or permanent repercussions as determined by other -members of the project's leadership. - -## Attribution - -This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html -[homepage]: https://www.contributor-covenant.org - -For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq -- 2.38.5 From 11a9a606ba66d04db766914e03fb5187551503cd Mon Sep 17 00:00:00 2001 From: ziproot Date: Mon, 25 Oct 2021 02:38:03 +0000 Subject: [PATCH 6/9] Add license Now it's actually open source. --- LICENSE | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 LICENSE diff --git a/LICENSE b/LICENSE new file mode 100644 index 0000000..6dc5eed --- /dev/null +++ b/LICENSE @@ -0,0 +1,7 @@ +Copyright 2021 ziproot + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. + +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. \ No newline at end of file -- 2.38.5 From 143e5ea5577c751f4669aed0321d514571abe346 Mon Sep 17 00:00:00 2001 From: ziproot Date: Mon, 25 Oct 2021 02:42:33 +0000 Subject: [PATCH 7/9] Delete 'LICENSE' --- LICENSE | 7 ------- 1 file changed, 7 deletions(-) delete mode 100644 LICENSE diff --git a/LICENSE b/LICENSE deleted file mode 100644 index 6dc5eed..0000000 --- a/LICENSE +++ /dev/null @@ -1,7 +0,0 @@ -Copyright 2021 ziproot - -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. - -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. \ No newline at end of file -- 2.38.5 From 2641f69e65ce4c86909fa6f2d75ee9cf26d45361 Mon Sep 17 00:00:00 2001 From: ziproot Date: Thu, 11 Nov 2021 04:52:02 +0000 Subject: [PATCH 8/9] Fix minor typo --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c9f575f..261ca69 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -18,7 +18,7 @@ Questions are things that you are unsure about. When in doubt, mark it as a ques ## Enhancements Enhancements are things you want to improve. Be sure to label it based on what type of enhancement it is: Security: This is an improvement to security you would like to see, such as RSA encryption. -QOL: This is an improvement to quality of life you would like to see, such as more lanugages as codes. If in doubt, mark it as QOL. +QOL: This is an improvement to quality of life you would like to see, such as more languages as codes. If in doubt, mark it as QOL. Documentation: This is an improvement to documentation you would like to see. Be sure to format the enhancement as dictated in the feature request template. # Pull Requests -- 2.38.5 From a281212a3f858db3126d66095a0dbb6b67e76238 Mon Sep 17 00:00:00 2001 From: ziproot Date: Thu, 2 Dec 2021 03:44:44 +0000 Subject: [PATCH 9/9] Now correctly mentions Gitea and not Github. --- SECURITY.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/SECURITY.md b/SECURITY.md index 2f539a2..4cfb94c 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -6,4 +6,4 @@ Always use the latest version to get the best security. Only the latest version ## Reporting a Vulnerability -Since this is an obsfucation program, if there's some security problem, that's either a bug or an enhancement. Report it using github features request and use the security label. +Since this is an obsfucation program, if there's some security problem, that's either a bug or an enhancement. Report it using gitea features request and use the security label. -- 2.38.5