Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: new92/instatools
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: new92/instatools
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: main
Choose a head ref
Loading
Showing with 124,655 additions and 2,849 deletions.
  1. +53 −77 CODE_OF_CONDUCT.md
  2. +62 −11 CONTRIBUTING.md
  3. BIN Chronos/Photos/menu.png
  4. BIN Chronos/Photos/output.png
  5. +36 −0 Chronos/README.md
  6. +400 −0 Chronos/chronos.py
  7. BIN Delta/Photos/menu.png
  8. BIN Delta/Photos/output.png
  9. BIN Delta/Photos/short_code_example.png
  10. +40 −0 Delta/README.md
  11. +382 −0 Delta/delta.py
  12. 0 Delta/shortcodes.txt
  13. BIN Hermes/Photos/menu.png
  14. BIN Hermes/Photos/output.png
  15. BIN Hermes/Photos/short_code_example.png
  16. +40 −0 Hermes/README.md
  17. +450 −0 Hermes/hermes.py
  18. BIN Hunter/Photos/menu.png
  19. BIN Hunter/Photos/output.jpg
  20. BIN Hunter/Photos/output_.png
  21. +43 −0 Hunter/README.md
  22. +437 −0 Hunter/hunter.py
  23. +0 −448 IsVer/IsVer.py
  24. BIN IsVer/Photos/isver.png
  25. BIN IsVer/Photos/menu.png
  26. BIN IsVer/Photos/output.png
  27. BIN IsVer/Photos/output_.png
  28. +34 −9 IsVer/README.md
  29. +0 −16 IsVer/config.json
  30. +459 −0 IsVer/isver.py
  31. BIN Kratos/Photos/menu.png
  32. BIN Kratos/Photos/output.jpg
  33. BIN Kratos/Photos/short_code_example.png
  34. +40 −0 Kratos/README.md
  35. +473 −0 Kratos/kratos.py
  36. 0 Kratos/shortcodes.txt
  37. +0 −586 Mutuals/Mutuals.py
  38. BIN Mutuals/Photos/menu.png
  39. BIN Mutuals/Photos/output.png
  40. BIN Mutuals/Photos/output_.png
  41. +37 −10 Mutuals/README.md
  42. +0 −16 Mutuals/config.json
  43. +551 −0 Mutuals/mutuals.py
  44. BIN Poirot/Photos/menu.png
  45. BIN Poirot/Photos/output.png
  46. +39 −0 Poirot/README.md
  47. +380 −0 Poirot/poirot.py
  48. +62 −80 README.md
  49. BIN Researcher/Photos/menu.png
  50. BIN Researcher/Photos/output.png
  51. +33 −3 Researcher/README.md
  52. +0 −449 Researcher/Researcher.py
  53. +0 −16 Researcher/config.json
  54. +114,566 −0 Researcher/files/cities.txt
  55. +98 −0 Researcher/files/countries.txt
  56. +520 −0 Researcher/researcher.py
  57. +1 −0 SECURITY.md
  58. BIN Spammer/Photos/menu.png
  59. +42 −0 Spammer/README.md
  60. +378 −0 Spammer/spammer.py
  61. 0 Spammer/targets.txt
  62. BIN Sphinx/Photos/data.png
  63. BIN Sphinx/Photos/menu.png
  64. BIN Sphinx/Photos/output.png
  65. BIN Sphinx/Photos/short_code_example.png
  66. +43 −0 Sphinx/README.md
  67. +2,229 −0 Sphinx/profanity.txt
  68. 0 Sphinx/shortcodes.txt
  69. +473 −0 Sphinx/sphinx.py
  70. BIN Spider/Photos/menu.png
  71. BIN Spider/Photos/output.png
  72. +41 −0 Spider/README.md
  73. +435 −0 Spider/spider.py
  74. BIN ToolZ/Photos/menu.png
  75. BIN ToolZ/Photos/output.png
  76. +35 −7 ToolZ/README.md
  77. +0 −463 ToolZ/ToolZ.py
  78. +0 −16 ToolZ/config.json
  79. +432 −0 ToolZ/toolz.py
  80. BIN Tracker/Photos/menu.png
  81. BIN Tracker/Photos/output.png
  82. BIN Tracker/Photos/tracker.png
  83. +37 −11 Tracker/README.md
  84. +0 −613 Tracker/Tracker.py
  85. +0 −16 Tracker/config.json
  86. +717 −0 Tracker/tracker.py
  87. BIN Zeus/Photos/menu.png
  88. BIN Zeus/Photos/output.png
  89. BIN Zeus/Photos/short_code_example.png
  90. +43 −0 Zeus/README.md
  91. 0 Zeus/shortcodes.txt
  92. +436 −0 Zeus/zeus.py
  93. +53 −0 cookies.py
  94. +5 −2 requirements.txt
  95. +20 −0 update.py
130 changes: 53 additions & 77 deletions CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -1,94 +1,70 @@
# Citizen Code of Conduct
# Code of Conduct - InstaTools

## 1. Purpose
## Our Pledge

A primary goal of Mutuals is to be inclusive to the largest number of contributors, with the most varied and diverse backgrounds possible. As such, we are committed to providing a friendly, safe and welcoming environment for all, regardless of gender, sexual orientation, ability, ethnicity, socioeconomic status, and religion (or lack thereof).
In the interest of fostering an open and welcoming environment, we as
contributors and maintainers pledge to make 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, or sexual identity and orientation.

This code of conduct outlines our expectations for all those who participate in our community, as well as the consequences for unacceptable behavior.
## Our Standards

We invite all those who participate in Mutuals to help us create safe and positive experiences for everyone.
Examples of behavior that contributes to a positive environment for our
community include:

## 2. Open [Source/Culture/Tech] Citizenship
* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community

A supplemental goal of this Code of Conduct is to increase open [source/culture/tech] citizenship by encouraging participants to recognize and strengthen the relationships between our actions and their effects on our community.
Examples of unacceptable behavior include:

Communities mirror the societies in which they exist and positive action is essential to counteract the many forms of inequality and abuses of power that exist in society.
* The use of sexualized language or imagery, and sexual attention or
advances
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

If you see someone who is making an extra effort to ensure our community is welcoming, friendly, and encourages all participants to contribute to the fullest extent, we want to know.
## Our Responsibilities

## 3. Expected Behavior
Project maintainers are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any instances of unacceptable behavior.

The following behaviors are expected and requested of all community members:
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.

* Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
* Exercise consideration and respect in your speech and actions.
* Attempt collaboration before conflict.
* Refrain from demeaning, discriminatory, or harassing behavior and speech.
* Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
* Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
## Scope

## 4. Unacceptable Behavior
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

The following behaviors are considered harassment and are unacceptable within our community:
## Enforcement

* Violence, threats of violence or violent language directed against another person.
* Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
* Posting or displaying sexually explicit or violent material.
* Posting or threatening to post other people's personally identifying information ("doxing").
* Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
* Inappropriate photography or recording.
* Inappropriate physical contact. You should have someone's consent before touching them.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Advocating for, or encouraging, any of the above behavior.
* Sustained disruption of community events, including talks and presentations.
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at .
All complaints will be reviewed and investigated promptly and fairly.

## 5. Weapons Policy
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

No weapons will be allowed at Mutuals events, community spaces, or in other spaces covered by the scope of this Code of Conduct. Weapons include but are not limited to guns, explosives (including fireworks), and large knives such as those used for hunting or display, as well as any other item used for the purpose of causing injury or harm to others. Anyone seen in possession of one of these items will be asked to leave immediately, and will only be allowed to return without the weapon. Community members are further expected to comply with all state and local laws on this matter.
## Attribution

## 6. Consequences of Unacceptable Behavior

Unacceptable behavior from any community member, including sponsors and those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If a community member engages in unacceptable behavior, the community organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event).

## 7. Reporting Guidelines

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. .



Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

## 8. Addressing Grievances

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.



## 9. Scope

We expect all community participants (contributors, paid or otherwise; sponsors; and other guests) to abide by this Code of Conduct in all community venues--online and in-person--as well as in all one-on-one communications pertaining to community business.

This code of conduct and its related procedures also applies to unacceptable behavior occurring outside the scope of community activities when such behavior has the potential to adversely affect the safety and well-being of community members.

## 10. Contact info

Please feel free to contact me at anytime via <a href="mailto:new92github@gmail.com">email</a>

## 11. License and attribution

The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).

Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).

_Revision 2.3. Posted 6 March 2017._

_Revision 2.2. Posted 4 February 2016._

_Revision 2.1. Posted 23 June 2014._

_Revision 2.0, adopted by the [Stumptown Syndicate](http://stumptownsyndicate.org) board on 10 January 2013. Posted 17 March 2013._
This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version
[1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and
[2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md),
and was generated by [contributing-gen](https://github.com/bttger/contributing-gen).
73 changes: 62 additions & 11 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,5 @@
# Contributing to Mutuals
<!-- omit in toc -->
# Contributing to InstaTools

First off, thanks for taking the time to contribute! ❤️

@@ -10,6 +11,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
> - Refer this project in your project's readme
> - Mention the project at local meetups and tell your friends/colleagues
<!-- omit in toc -->
## Table of Contents

- [Code of Conduct](#code-of-conduct)
@@ -27,7 +29,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
## Code of Conduct

This project and everyone participating in it is governed by the
[Mutuals Code of Conduct](https://github.com/new92/Mutualsblob/master/CODE_OF_CONDUCT.md).
[InstaTools Code of Conduct](https://github.com/new92/InstaToolsblob/master/CODE_OF_CONDUCT.md).
By participating, you are expected to uphold this code. Please report unacceptable behavior
to .

@@ -36,30 +38,46 @@ to .

> If you want to ask a question, we assume that you have read the available [Documentation]().
Before you ask a question, it is best to search for existing [Issues](https://github.com/new92/Mutuals/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
Before you ask a question, it is best to search for existing [Issues](https://github.com/new92/InstaTools/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.

If you then still feel the need to ask a question and need clarification, we recommend the following:

- Open an [Issue](https://github.com/new92/Mutuals/issues/new).
- Open an [Issue](https://github.com/new92/InstaTools/issues/new).
- Provide as much context as you can about what you're running into.
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.

We will then take care of the issue as soon as possible.

<!--
You might want to create a separate issue tag for questions and include it in this description. People should then tag their issues accordingly.
Depending on how large the project is, you may want to outsource the questioning, e.g. to Stack Overflow or Gitter. You may add additional contact and information possibilities:
- IRC
- Slack
- Gitter
- Stack Overflow tag
- Blog
- FAQ
- Roadmap
- E-Mail List
- Forum
-->

## I Want To Contribute

> ### Legal Notice
> ### Legal Notice <!-- omit in toc -->
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
### Reporting Bugs

<!-- omit in toc -->
#### Before Submitting a Bug Report

A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.

- Make sure that you are using the latest version.
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](). If you are looking for support, you might want to check [this section](#i-have-a-question)).
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/new92/Mutualsissues?q=label%3Abug).
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](https://github.com/new92/InstaToolsissues?q=label%3Abug).
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
- Collect information about the bug:
- Stack trace (Traceback)
@@ -68,13 +86,15 @@ A good bug report shouldn't leave others needing to chase you up for more inform
- Possibly your input and the output
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?

<!-- omit in toc -->
#### How Do I Submit a Good Bug Report?

> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to .
<!-- You may add a PGP key to allow the messages to be sent encrypted as well. -->
We use GitHub issues to track bugs and errors. If you run into an issue with the project:

- Open an [Issue](https://github.com/new92/Mutuals/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
- Open an [Issue](https://github.com/new92/InstaTools/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
- Explain the behavior you would expect and the actual behavior.
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
- Provide the information you collected in the previous section.
@@ -85,24 +105,55 @@ Once it's filed:
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).

<!-- You might want to create an issue template for bugs and errors that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->


### Suggesting Enhancements

This section guides you through submitting an enhancement suggestion for Mutuals, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
This section guides you through submitting an enhancement suggestion for InstaTools, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.

<!-- omit in toc -->
#### Before Submitting an Enhancement

- Make sure that you are using the latest version.
- Read the [documentation]() carefully and find out if the functionality is already covered, maybe by an individual configuration.
- Perform a [search](https://github.com/new92/Mutuals/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Perform a [search](https://github.com/new92/InstaTools/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.

<!-- omit in toc -->
#### How Do I Submit a Good Enhancement Suggestion?

Enhancement suggestions are tracked as [GitHub issues](https://github.com/new92/Mutuals/issues).
Enhancement suggestions are tracked as [GitHub issues](https://github.com/new92/InstaTools/issues).

- Use a **clear and descriptive title** for the issue to identify the suggestion.
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux. <!-- this should only be included if the project has a GUI -->
- **Explain why this enhancement would be useful** to most Mutuals users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
- **Explain why this enhancement would be useful** to most InstaTools users. You may also want to point out the other projects that solved it better and which could serve as inspiration.

<!-- You might want to create an issue template for enhancement suggestions that can be used as a guide and that defines the structure of the information to be included. If you do so, reference it here in the description. -->

### Your First Code Contribution
<!-- TODO
include Setup of env, IDE and typical getting started instructions?
-->

### Improving The Documentation
<!-- TODO
Updating, improving and correcting the documentation
-->

## Styleguides
### Commit Messages
<!-- TODO
-->

## Join The Project Team
<!-- TODO -->

<!-- omit in toc -->
## Attribution
This guide is based on the **contributing-gen**. [Make your own](https://github.com/bttger/contributing-gen)!
Binary file added Chronos/Photos/menu.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added Chronos/Photos/output.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading