Tinder Osint Users

◦ Easy Search Users by filters!

◦ Developed with the software and tools listed below.

RECOMNDED: Use extension SpoofGeolocation to change gps location

📒 Table of Contents

• 📒 Table of Contents
• 📍 Overview
• ⚙️ Features
• 📂 Project Structure
• 🧩 Modules
• 🚀 Getting Started
• 🗺 Roadmap
• 🤝 Contributing
• 📄 License
• 👏 Acknowledgments

---

📍 Overview

This project is an extension for chromium designed to automate the search of people according to their name and age in the dating application Tinder. The operation is based on accessing the tinder page, spoofing the location and in the area to make matches, it searches by matching the name, then allows you to filter by age, if you do not want to put age filter within the extension leaves the age at 0. It is recommended to put the following settings on the tinder page:

• Distance preferences: <range of 1 to 3 Km>;
• Show me only people in that range: True;
• I am interested in: <Gender of user to search for>;
• Age preference: <age range to quickly discard very low or very high ages>;

Recommendations:

• For geolocation position three profiles in three different points to triangulate the user.

---

⚙️ Features

Feature	Description
⚙️ Architecture	The system follows a Chrome extension architecture, with separate background and content scripts. The content script is injected into specific webpages, while the background script listens for icon clicks and sends messages to the content script.
📖 Documentation	The documentation is minimal. It provides brief descriptions of the files and their functions, but lacks detailed explanations of the system's functionality.
🔗 Dependencies	The system relies on the Google Chrome browser and the chrome.tabs API for proper functioning. No external libraries or systems are used.
🧩 Modularity	The system is well-organized into smaller components, with a separate script for each specific functionality. The scripts can be easily maintained and modified as needed.
⚡️ Performance	The system's performance largely depends on Chrome's processing capabilities. It does not seem to have any specific optimizations for speed, efficiency, or resource usage.
🔐 Security	The system does not implement any specific security measures to protect user data or maintain functionality. The focus is on automating actions in a specific web application, which doesn't involve significant security concerns.
🔀 Version Control	The codebase is version controlled using Git. The GitHub repository provides version history, issues, and pull requests to enable collaboration and track changes over time.
🔌 Integrations	The system primarily interacts with the Google Chrome browser through the chrome.tabs API. It does not have any direct integrations with other external systems or services.
📶 Scalability	The system's scalability is limited to its use as a Chrome extension. It can potentially be enhanced with additional features or expanded for other web applications, but significant changes would be required for that purpose.

---

📂 Project

Root

File	Summary
background_script.js	This code snippet is for a Chrome extension. It toggles the activation of a content script on a specific tab when the extension's icon is clicked. The content script is executed when enabled and deactivated when disabled. The icon changes accordingly to indicate the script's state.
content_script.js	The code allows for clicking on a specific element on a webpage at regular intervals. It also includes functionality to toggle the header, enabling or disabling the script's execution. This code is designed specifically for use with the Google Chrome browser.
popup.html	This code is a HTML document that creates a webpage for a Tinder AutoLike extension. It contains a title, a button to activate the extension, and a link to the GitHub project. It also includes CSS styling for the button and list items. The JavaScript file "popup_script.js" is linked for additional functionality.
popup_script.js	This code listens for the DOMContentLoaded event and adds a click event listener to a button element with the id "toggleButton". When clicked, the code sends a message to the active tab in the Chrome browser using the chrome.tabs API. It also updates the button text based on the response from the content script. If the header is enabled, the button text is "Desactivar", otherwise it is "Activar" and the tab is reloaded.

---

🚀 Getting Started

✔️ Prerequisites

Before you begin, make sure you have the following prerequisites installed:

• ℹ️ Chromium-based Browser (Chrome, Chromium, Edge, Brave, Firefox [Chromium-based only],...)
• ℹ️ Tinder Account

📦 Installation

1. Clone the Tinder-Osint-Tool repository:

git clone https://github.com/j0rd1s3rr4n0/Tinder-Osint-Tool

2. Change to the project directory:

cd Tinder-Osint-Tool

3. Install the dependencies:

• Go to <browser-name>://extensions
• Enable Developer Mode
• Click on Load uncompressed
• Select Tinder-Osint-Tool folder

🎮 Using Tinder-Osint-Tool

1. Go to https://tinder.com/app/recs

   • Log-In / Sign-In.
   • Change Configuration Configuration Info.
   • Click any part of the webpage and go to the main page to swipe.

2. Click on the Extension Icon

3. Fill out the Form

4. Press Activate to activate and Deactivate to deactivate.

---

🤝 Contributing

Contributions are always welcome! Please follow these steps:

1. Fork the project repository. This creates a copy of the project on your account that you can modify without affecting the original project.
2. Clone the forked repository to your local machine using a Git client like Git or GitHub Desktop.
3. Create a new branch with a descriptive name (e.g., new-feature-branch or bugfix-issue-123).

git checkout -b new-feature-branch

4. Make changes to the project's codebase.
5. Commit your changes to your local branch with a clear commit message that explains the changes you've made.

git commit -m 'Implemented new feature.'

6. Push your changes to your forked repository on GitHub using the following command

git push origin new-feature-branch

7. Create a new pull request to the original project repository. In the pull request, describe the changes you've made and why they're necessary. The project maintainers will review your changes and provide feedback or merge them into the main branch.

---

📄 License

This project is licensed under the ℹ️ INSERT-LICENSE-TYPE License. See the LICENSE file for additional info.

---

👏 Acknowledgments

• ℹ️ List any resources, contributors, inspiration, etc.

---