- From: Cecylia Bocovich via GitHub <sysbot+gh@w3.org>
- Date: Fri, 03 Sep 2021 16:36:41 +0000
- To: public-webrtc-logs@w3.org
Hi! We have a web-extension called Snowflake available for Firefox and Chrome that we are in the process of updating from v2 to v3 manifests. This update requires the use of `RTCPeerConnection` in service workers: - https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/ - https://chrome.google.com/webstore/detail/snowflake/mafpmfcccpbjnhfhjnllmmalhifmlcie Snowflake is a censorship circumvention tool for Tor: https://snowflake.torproject.org/ We use the web extension to allow people to run anti-censorship proxies from their browser to provide access to the Tor network. This has allowed us to distribute over 10,000 unique proxy IPs, making Snowflake one of the most effective and scalable means to access the Tor network in places with the strictest censorship practices. The web extension functions by constantly polling a Snowflake distributor (also called a broker) for clients that need to connect to Snowflake proxies. When a client is matched with a user's web-extension, a PeerConnection is automatically created in the background and the data channel used to tunnel the client's Tor traffic through the WebRTC connection. This occurs constantly and automatically in the background to allow users to run proxies as long as their web browser remains open and without any manual input required on their part. Thus, we require the ability to create a PeerConnection in the background process. Hopefully this use-case is useful in motivating the issue. Is there anything else we can do to help move this forward? -- GitHub Notification of comment by cohosh Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/77#issuecomment-912667886 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 3 September 2021 16:36:43 UTC