This was an experimental feature that monitored website changes via a JavaScript snippet. The experiment has concluded and this integration is no longer supported.
How the Script Worked
When installed, the script automatically:
- Normalizes Page Content: Removes dynamic elements (e.g., scripts, styles, comments, inline event handlers) to focus on stable content.
- Generates a Hash: Creates a unique hash of the normalized content using the FNV-1a algorithm to represent the page's state.
- Checks for Changes: Compares the current hash with the previously stored hash (saved in localStorage).
- Rate-Limits Execution:
- Runs only if at least 5 minutes have passed since the last check.
- Limited to 12 runs per day to avoid excessive API calls.
- Reports Changes: If a change is detected (hash mismatch or no recent hash), it sends a POST request to https://api.vibe-eval.com/continuous-testing with the new hash and site hostname.
- Stores the Hash: Saves the new hash and timestamp in localStorage to track the page's state.
Privacy Considerations:
- The script only sends a hash of the content, not the content itself, ensuring no sensitive data is transmitted.
- The hostname of your site is included to identify the source.
Rate-Limiting and Change Reporting
The script was designed to minimize server load and API usage:
- 5-Minute Cooldown: The script skips execution if a check was performed within the last 5 minutes (300,000 milliseconds).
- 12 Runs Per Day: A daily counter ensures no more than 12 checks occur in a 24-hour period (resetting at midnight UTC).
- Change-Only Reporting: The script only sends a request to the API if:
- The content hash has changed (indicating a page update).
- No hash exists in localStorage (first visit or cleared storage).
- The stored hash is older than 24 hours (expired).
This ensured efficient operation and prevented unnecessary API calls.