We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For flashproxy, we have an npm package (npm install flashproxy) that runs proxies headlessly. https://www.npmjs.com/package/flashproxy
npm install flashproxy
The posting on tor-dev today suggests we should consider the same for snowflake, https://lists.torproject.org/pipermail/tor-dev/2016-March/010576.html
We could reuse the same code for both, as we did above, with node-webrtc, or reimplement it with go-webrtc.
go-webrtc
The text was updated successfully, but these errors were encountered:
Standalone snowflake
e295556
* Start of #30
I'm able to bootstrap tor with e295556 from node, but wrtc seems like a pretty unreliable library. It segfaults every time I close the datachannel.
Sorry, something went wrong.
A go version was implemented in #41
Use atomic for local/remote epoch
45d2ee1
Race was reported around set/get of epoch, instead of juggling mutex just use an atomic Resolves #30
No branches or pull requests
For flashproxy, we have an npm package (
npm install flashproxy
) that runs proxies headlessly.https://www.npmjs.com/package/flashproxy
The posting on tor-dev today suggests we should consider the same for snowflake,
https://lists.torproject.org/pipermail/tor-dev/2016-March/010576.html
We could reuse the same code for both, as we did above, with node-webrtc, or reimplement it with
go-webrtc
.The text was updated successfully, but these errors were encountered: