Compare commits

...

11 Commits

Author SHA1 Message Date
ziproot a281212a3f Now correctly mentions Gitea and not Github. 2021-12-02 03:44:44 +00:00
ziproot 2641f69e65 Fix minor typo 2021-11-11 04:52:02 +00:00
ziproot 143e5ea557 Delete 'LICENSE' 2021-10-25 02:42:33 +00:00
ziproot 11a9a606ba Add license
Now it's actually open source.
2021-10-25 02:38:03 +00:00
ziproot ecd7226433 Remove Code of Conduct 2021-10-25 02:35:31 +00:00
PeacefulPotato e17d209ece Update to 1.0.2.1: Clarify more apps that the markdown optimization feature supports 2021-02-09 19:07:53 +00:00
PeacefulPotato b624f8c39b Fix typos 2021-02-09 19:04:55 +00:00
PeacefulPotato e8eafd2cee
Update CONTRIBUTING.md 2020-12-04 15:11:48 -05:00
PeacefulPotato 13b5ed9044
Create pull_request.md 2020-12-04 15:09:30 -05:00
PeacefulPotato 57abbfaac6
Merge pull request #3 from PeacefulPotato/issue-templates
Create issue templates
2020-12-04 15:04:42 -05:00
PeacefulPotato 8a3e27d269 Create issue templates 2020-12-04 15:04:27 -05:00
8 changed files with 114 additions and 74 deletions

42
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View File

@ -0,0 +1,42 @@
---
name: Bug report
about: Something broke? Let us know here!
title: ''
labels: bug
assignees: ''
---
<!-- PLEASE MAKE SURE YOUR ISSUE DOESN'T ALREADY EXIST! -->
<!-- PLEASE ADD THE SECURITY LABEL IF THE BUG IS SECURITY RELATED! -->
**Issue Description**
A clear and concise description of what the bug is.
**System Details**
* HOP program (such as HOP.1.0.2.py)
* Python version (such as python 3.9)
* Platform name (such as repl.it)
**Steps To Reproduce**
Steps to reproduce the behavior. Should be easy to follow.
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Actual behavior**
A clear and concise description of what actually happened.
**Exception**
```
If the bug is an exception, enter it here.
```
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here

View File

@ -0,0 +1,25 @@
---
name: Feature request
about: Something you don't like? Let us know here!
title: ''
labels: enhancement
assignees: ''
---
<!-- PLEASE MAKE SURE YOUR ISSUE DOESN'T ALREADY EXIST! -->
<!-- PLEASE ASSIGN A RELAVENT LABEL AS DICTATED IN CONTRUBUTING.MD! -->
**Problem**
Something you are missing or do not like about HOP. Be clear and concise.
**Preferred Solution**
Your preferred method of addressing this problem. Be specific. Go into detail on how this solution can be reached.
**Alternate Solutions**
List alternate solutions you considered and why you would rather do your preferred solution.
**Screenshots**
If applicable, add screenshots to help explain your solution.
**Additional context**
Add any other context about the feature request here.

28
.github/ISSUE_TEMPLATE/question.md vendored Normal file
View File

@ -0,0 +1,28 @@
---
name: Question
about: Something you're unsure about? Let us know here!
title: ''
labels: question
assignees: ''
---
<!-- PLEASE MAKE SURE YOUR ISSUE DOESN'T ALREADY EXIST! -->
<!-- ALWAYS TRY TO ANSWER A QUESTION YOURSELF IF POSSIBLE! -->
**Question**
What do you want to know? Be clear and concise.
**Self Research**
Explain what you have already tried to do before asking the question.
**System Details**
* HOP program (such as HOP.1.0.2.py)
* Python version (such as python 3.9)
* Platform name (such as repl.it)
**Screenshots**
If applicable, add screenshots to help explain your question.
**Additional context**
Add any other context about the question here.

View File

@ -0,0 +1,7 @@
<!-- PLEASE BE SURE TO FOLLOW ALL DIRECTIONS IN CONTRIBUTING.MD BEFORE POSTING! -->
**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.

View File

@ -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

View File

@ -1,5 +1,5 @@
# Issues
There are three types of issues: Bugs, Questions and Enhcanements.
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,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 dictated in the feature request template.
## 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.
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 label the enhancement based on 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).
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.

View File

@ -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

View File

@ -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.