You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Once we have Tor working, we should consider using it for analytics.
When a user opts in to report analytics, we should consider sending that info over Tor If Brave is connecting to an analytics service or proxy over Tor, we should probably configure that as an onion service on our end. Should we use a single onion service rather than a full hidden service? We should consider using something like Alec Muffett's Enterprise Onion Toolkit on the infrastructure side.
Tor — even a single onion service — is still probably slower than a regular connection. However, analytics are non-interactive, and shouldn't be time-sensitive on the order of seconds to minutes of connection difference.
The text was updated successfully, but these errors were encountered:
Once we have Tor working, we should consider using it for analytics.
When a user opts in to report analytics, we should consider sending that info over Tor If Brave is connecting to an analytics service or proxy over Tor, we should probably configure that as an onion service on our end. Should we use a single onion service rather than a full hidden service? We should consider using something like Alec Muffett's Enterprise Onion Toolkit on the infrastructure side.
Tor — even a single onion service — is still probably slower than a regular connection. However, analytics are non-interactive, and shouldn't be time-sensitive on the order of seconds to minutes of connection difference.
The text was updated successfully, but these errors were encountered: