← Back to context Comment by dgellow 2 years ago https://radicle.xyz/ 3 comments dgellow Reply ekianjo 2 years ago close but it does not use Bittorrent for the P2P part? miohtama 2 years ago Bittorrent as a distribution protocol is not suitable for Git-like traffic, so Radicle is doing their own p2p. alurm 2 years ago As I understand, Bittorrent is not a persistent data structure. Git and IPFS are. Radicle is another interesting approach. They used IPFS but switched to a custom protocol, as I understand, for performance.
ekianjo 2 years ago close but it does not use Bittorrent for the P2P part? miohtama 2 years ago Bittorrent as a distribution protocol is not suitable for Git-like traffic, so Radicle is doing their own p2p. alurm 2 years ago As I understand, Bittorrent is not a persistent data structure. Git and IPFS are. Radicle is another interesting approach. They used IPFS but switched to a custom protocol, as I understand, for performance.
miohtama 2 years ago Bittorrent as a distribution protocol is not suitable for Git-like traffic, so Radicle is doing their own p2p.
alurm 2 years ago As I understand, Bittorrent is not a persistent data structure. Git and IPFS are. Radicle is another interesting approach. They used IPFS but switched to a custom protocol, as I understand, for performance.
close but it does not use Bittorrent for the P2P part?
Bittorrent as a distribution protocol is not suitable for Git-like traffic, so Radicle is doing their own p2p.
As I understand, Bittorrent is not a persistent data structure. Git and IPFS are. Radicle is another interesting approach. They used IPFS but switched to a custom protocol, as I understand, for performance.