I know that there is also a web-frontend (kinda like GitHub) for radicle: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA.... But I haven't seen a guide how to set that web frontend up locally.
We'll be also working on packaging the js bundle so that it can be distributed and served locally without setting up a dev environment in the future.
https://app.radicle.xyz/nodes/127.0.0.1:8080/rad:z3gqcJUoA1n...
Looks like 1.0.0-rc.1 was just released yesterday.
For the average GitHub user, it adds a lot of complexity for undetermined benefit. It basically ensures your repositories can’t get pulled if someone at Microsoft doesn’t like what you’re doing.
I'm not certain you're using it in a pejorative manner, or just neutrally, but in any case, it's funny to see on here.
> 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?
