WHERE IS MY DUDE (Documentation)

Quick Start

WHERE IS MY DUDE is a specialized automation tool designed to locate and track specific data points or assets across your digital environment. This quick start guide will help you set up the core components and run your first tracking session in just a few steps.

Installation & Setup

1. Prepare the Environment: Ensure you have the necessary runtime installed on your machine. This tool is optimized for high-performance data scanning and requires a stable local directory for storing configuration files.
2. Initialize the Directory: Create a dedicated folder for your project. Place the core script files and your data sources into this directory to ensure the tool can index them correctly.
3. Configure Access: If you are tracking data across external platforms, ensure your API keys or access tokens are correctly placed in your local environment variables.

Running Your First Scan

1. Launch the Tool: Open your command interface and navigate to the project folder.
2. Execute Command: Run the primary execution script. The tool will begin scanning the defined parameters immediately.
3. Monitor Progress: A live terminal output will display the current status.
   • SEARCHING: The tool is actively parsing data.
   • FOUND: The specific asset or data point has been located.
   • ERROR: A connection or parsing issue occurred.
4. Review Results: Once the scan is complete, a summary report is generated in your project folder for detailed analysis.

The Two Files — WHERE IS MY DUDE

Core Architecture

The functionality of WHERE IS MY DUDE relies on two critical files that must exist in your root directory. These files work in tandem to define the “what” and “how” of your tracking operations.

1. The Configuration File (config.json)

This file acts as the brain of the operation. It stores all the persistent settings that dictate the tool’s behavior:

• Target Parameters: Defines the specific keywords, IDs, or asset names the tool is searching for.
• Scan Intervals: Sets how frequently the tool should refresh its search (e.g., every 60 seconds).
• Notification Hooks: Contains the webhook URLs or email settings used to alert you when a target is found.
• API Credentials: Stores the encrypted references needed to access protected data streams.

2. The Source File (sources.txt)

While the config file handles the logic, the source file provides the raw data locations. It is a plain-text list of every environment the tool should monitor:

• Directory Paths: Local folders or network drives.
• URL Lists: Specific web endpoints or cloud storage links.
• Database Strings: Connection points for SQL or NoSQL environments.

File Management Best Practices

• Integrity: Do not rename these files. The tool is hard-coded to look for these specific filenames upon startup.
• Backups: Always keep a copy of your config.json. If you move to a new machine, simply dropping these two files into the new directory will restore your entire tracking setup.
• Security: Since these files may contain sensitive path information or access tokens, ensure they are stored in a secure, non-public directory.

FEATURES

Key Features — WHERE IS MY DUDE

Core Capabilities

WHERE IS MY DUDE provides a robust suite of tools designed for precision tracking and automated environment monitoring. The platform is built to handle complex data sets while maintaining a high level of performance and accuracy.

• Real-Time Data Indexing: The tool continuously scans your defined local and cloud sources, ensuring that the information you are tracking is updated without manual intervention.
• Intelligent Pattern Recognition: Beyond simple keyword matching, the system utilizes advanced algorithms to identify assets based on partial data strings or metadata signatures.
• Custom Notification Webhooks: Integrate your tracking results with third-party applications like Slack, Discord, or custom API endpoints to receive instant alerts the moment a target is located.
• Historical Logging: Every successful find and every scan attempt is recorded in a local log file, allowing you to audit the tool’s performance and track asset movement over time.
• Resource Efficiency: Optimized for low-latency operations, the tool is designed to run in the background with minimal impact on your system’s CPU and memory.

Geofence Zones — WHERE IS MY DUDE

Defining Search Boundaries

Geofence Zones allow you to restrict the tool’s operations to specific digital or logical perimeters. This ensures that your scans remain focused and do not leak into unauthorized or irrelevant data environments.

How Geofencing Works

1. Zone Creation: Within your config.json, you can define “Safe Zones” and “Exclude Zones.”
2. Path Restriction: When the tool encounters a directory or a URL that falls within an Exclude Zone, it will bypass that data stream entirely, saving time and processing power.
3. Cross-Boundary Alerts: You can configure the tool to send a high-priority alert if a tracked asset is found outside of its designated Safe Zone.

Benefits of Geofencing

• Enhanced Privacy: Prevent the tool from scanning sensitive folders that are not relevant to your current project.
• Targeted Accuracy: Increase the speed of your scans by narrowing the search area to only the most likely locations.
• Compliance: Ensure your data tracking activities adhere to organizational or legal boundaries by strictly defining where the tool is permitted to operate.

Configuring Your First Zone

To set up a zone, open your configuration file and locate the boundaries object. Here, you can list the specific paths or domain patterns that the tool should either prioritize or avoid during its next active session.

HELP:

FAQ — WHERE IS MY DUDE

Common Questions & Operations

• How often does the tool scan for assets? The scan frequency is determined by the interval setting in your config.json file. You can set this to check as often as every 60 seconds or at longer intervals depending on your needs.
• Can I track multiple types of data at once? Yes. You can define various keywords, unique IDs, or specific asset names within the target_parameters section of your configuration. The tool will monitor all listed items simultaneously across your defined sources.
• What happens if a source becomes unavailable? If the tool cannot reach a directory or URL listed in your sources.txt, it will log a connection error and skip to the next available source. It will attempt to reconnect during the next scheduled scan interval.
• Is my data sent to an external server? No. WHERE IS MY DUDE operates as a local automation tool. All scanning logic and result logging stay within your local environment, ensuring your path information and access tokens remain private.

Troubleshooting — WHERE IS MY DUDE

Resolving Common Issues

• Problem: The tool fails to start or says “Missing Files” * Check Filenames: Ensure your configuration files are named exactly config.json and sources.txt. The tool is hard-coded to look for these specific names.
  • Directory Location: Both files must be placed in the same root directory as the execution script.
• Problem: No results are being found * Verify Sources: Check sources.txt to ensure the paths or URLs are correct and accessible from your current network.
  • Validate Parameters: Ensure the keywords or IDs in config.json match the metadata or content of the assets you are searching for.
  • Geofence Settings: Check if the area you are searching has been accidentally added to an “Exclude Zone” in your boundaries configuration.
• Problem: Notification alerts are not arriving * Webhook URL: Double-check the webhook link in your config.json for typos.
  • Network Permissions: Ensure your firewall or antivirus is not blocking the tool from sending outgoing data to your notification provider (e.g., Slack or Discord).

Technical Support If these steps do not resolve your issue, please check the local log file in your project folder for specific error codes. For further assistance, contact the development team with a copy of your log output for a faster resolution.