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
I have some concerns regarding privacy and tracking. As of now, CacheP2P "just works", without consent from the end-user. As this relies on P2P and torrent protocols, it's easy for anyone to track all IPs who accessed a page.
With some effort, an entity could reliably tell which pages a given IP has accessed, thus invalidating any possible privacy which could be had just by hitting a central server with https enabled. CacheP2P makes it easy for anyone to do this, so I believe it's important to discuss: is there anything CacheP2P can do to honor an user's request not to be part of the swarm?
It should be easy and not assume any technical knowledge from the user. That way, CacheP2P can be deployed on services which would benefit from the swarm availability, while allowing users who want to be private not to participate at all. This could work as an opt-in or opt-out, with opt-in preferred.
The text was updated successfully, but these errors were encountered:
I'm not sure that this behavior belongs in the core library though. It might be sufficient to strongly suggest that developers get user's consent and provide a small library that implements the UI as a banner.
I think that the concerns are valid. What @deckar01 proposes about facilitating the display of a small banner so that users can opt-in or out would be a good solution. And make it clear to developers that it's important for them to inform their users about the use of this kind of technologies.
I have some concerns regarding privacy and tracking. As of now, CacheP2P "just works", without consent from the end-user. As this relies on P2P and torrent protocols, it's easy for anyone to track all IPs who accessed a page.
With some effort, an entity could reliably tell which pages a given IP has accessed, thus invalidating any possible privacy which could be had just by hitting a central server with https enabled. CacheP2P makes it easy for anyone to do this, so I believe it's important to discuss: is there anything CacheP2P can do to honor an user's request not to be part of the swarm?
It should be easy and not assume any technical knowledge from the user. That way, CacheP2P can be deployed on services which would benefit from the swarm availability, while allowing users who want to be private not to participate at all. This could work as an opt-in or opt-out, with opt-in preferred.
The text was updated successfully, but these errors were encountered: