This is just an idea for now, exact details may change over time.
Describe the solution you'd like
Collect user internet speed, upload & download on software boot without interrupting the user experience.
Generate a Session ID for each proxy checking cycle that is started.
Send a request to our API containing the following information when the user starts the proxy-checking:
User's internet speed
Total ram
Available ram
CPU usage
CPU type
Session ID
Protocols being checked
Timeout being used
Number of retries configured
Keep alive turned on/off
Number of proxies being checked
Collect the following data periodically during the proxy-checking, and send an array to an API endpoint when the checking has ended, thus allowing us to create a timeline of the resource usage during the checking:
Software CPU usage
Software ram usage
Total CPU usage
Total ram usage
Send the amount of working and non-working proxies to an API endpoint when the checking has ended.
To be determined: send an encrypted version of each proxy to our endpoint, allowing us to determine if the user is checking our paid proxies, free proxies, or other, without exposing the proxy itself.
When the software first boots, the user should receive the option to opt-out of the analytical data.
Additional context
We want to collect data about the user's device & about the proxies so we can determine what the best proxy-checking conditions are to further help our customers in the future, such as how much ram is needed and how many threads are appropriate for the available resources.
This is just an idea for now, exact details may change over time.
Describe the solution you'd like
Collect user internet speed, upload & download on software boot without interrupting the user experience.
Generate a Session ID for each proxy checking cycle that is started.
Send a request to our API containing the following information when the user starts the proxy-checking:
Collect the following data periodically during the proxy-checking, and send an array to an API endpoint when the checking has ended, thus allowing us to create a timeline of the resource usage during the checking:
Send the amount of working and non-working proxies to an API endpoint when the checking has ended.
To be determined: send an encrypted version of each proxy to our endpoint, allowing us to determine if the user is checking our paid proxies, free proxies, or other, without exposing the proxy itself.
When the software first boots, the user should receive the option to opt-out of the analytical data.
Additional context We want to collect data about the user's device & about the proxies so we can determine what the best proxy-checking conditions are to further help our customers in the future, such as how much ram is needed and how many threads are appropriate for the available resources.
Users are free to discuss this.