[binary132]

I don’t think I understand how this protocol is supposed to solve the problems of the commons that arise in any peer to peer app, such as how to deal with malicious or misbehaving peers, illegal or unsavory content, and so on. Every P2P app needs to put those problems front and center in their design and I never feel the proposed solutions are adequate. But in this case, I simply don’t see them acknowledged at all.

[vaylian]

I'm still trying to get a deeper understanding of Radicle, but let me try to answer with what my current understanding is:

> how to deal with malicious or misbehaving peers

Radicle makes heavy use of public keys and signed data. Every user and every repository has an ID that is tied to some cryptographic key.

> illegal or unsavory content

Each peer can choose what to seed/mirror. Sidenote: The docs describe the number of seeders as an alternative metric for GitHub stars. The Radicle project also has a peer that tries to seed all repositories in order to promote the protocol.

@binary132: Are there some specific problems that you want to know how Radicle addresses them?

[binary132]

Ok; maybe it has a good set of problems it solves for and clearly documented solutions to them. I just didn’t see a front-and-center treatment of them, or really any. Maybe that’s just me, but I really think any p2p platform needs to be clear to its users about these things. I know I definitely haven’t thought comprehensively of what I might need to be aware of.