3 ms·
Related question: what is the best way to publish code so it is censorship resistant?
by xyzal 6y ago
Related question: what is the best way to publish code so it is censorship resistant?
- Fnoord 6y agoI don't claim to have the solution to your question but here's my proposal: Release it in two ways simultaneously. One, public, going for maximum exposure. This causes (short-term) availability. Assume this channel can get compromised at any time. Ie. clearweb. Two, at the same time, a more censorship resistant solution such as Tor or IPFS. Ie. darkweb. At the very least you should research the second option beforehand. I'd say though, if you already include the address in say your GitHub, then this allows caching beforehand hence a smoother transition. I saw this recently applied in alt-right movement. People getting banned from Twitter and Facebook already mentioning their contact info on darkweb beforehand cause they saw it coming.
- Snawoot 6y agoYep, this is exactly how we publish patch suite which unlocks NVENC sessions and NvFBC on Nvidia drivers: https://github.com/keylase/nvidia-patch https://github.com/keylase/nvidia-patch IPFS mirrors: Site: https://ipfs.io/ipns/QmYTEwv2GjQhtdN9bDfpLfQrVD7YLb1Sbh8igX8cEe9hHF/ https://ipfs.io/ipns/QmYTEwv2GjQhtdN9bDfpLfQrVD7YLb1Sbh8igX8... Git: git clone https://ipfs.io/ipns/Qmed4r8yrBP162WK1ybd1DJWhLUi4t6mGuBoB9fLtjxR7u nvidia-patch