Live data from Hacker News

Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

app.radicle.xyz

141–150 of 299 posts

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#141

Their monetization strategy is pretty critical for people who’d sink their time into the service and entrust it with the code for long-running projects. So… how do they plan on making money off of this? If they can’t or won’t say, what sort of projects do they imagine they’d attract in spite of that? (e.g. ephemeral ones? Data sets about current events?) Downvoters: do you not think their monetization strategy is imp…

this is a very VC-brained comment to make on a peer-to-peer open source project. let's instead ask if there are any single points of failure to the protocol and service, and if so, are those sustainable regarding developer time, effort, and compensation?

Incredible. They throw some indie-sounding buzzwords out and that's enough to make the business model unimpeachable?

Over the past few decades we've seen many cynical capitalists riding the wave of "peer to peer open source" for personal gain. It's absolutely within scope to discuss how a company's business model may affect their ability to deliver on the supposed mission.

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#142
post #135

I wonder how discoverable (for normal people) these repositories are. It looks like https://app.radicle.xyz/robots.txt doesn't exist, so it seems like fair game for search engines, and indeed a search on Google and DDG for site:app.radicle.xyz does give some results. Maybe not that high up yet if not using that site filter, perhaps the ranking will improve? Tools for integrating CI support with this would also be nic…

We are actually working on a number of CI integrations and building our own native one, for our needs.

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#143

Hi HN. I am the co-founder of the project. If you are interested in how the protocol works under the hood, start here: https://docs.radicle.xyz/ Docs are still WIP though.

My eyes! The goggles do nothing! [1] Please bring on some design and UX folks. The contrast literally strains the eyes.

[1] https://www.youtube.com/watch?v=PWFF7ecArBk

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#144
post #135

I wonder how discoverable (for normal people) these repositories are. It looks like https://app.radicle.xyz/robots.txt doesn't exist, so it seems like fair game for search engines, and indeed a search on Google and DDG for site:app.radicle.xyz does give some results. Maybe not that high up yet if not using that site filter, perhaps the ranking will improve? Tools for integrating CI support with this would also be nic…

It's a good point - I think "gateways" such as `app.radicle.xyz` will have to allow crawlers to index the full set of repositories on the network.

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#145
post #77

Earlier quoted context omitted.

Does that matter if the signatures are valid?

Yeah, because for eg. I can publish the given repository from my server with an additional signed commit (signed by me) on top of the original history, and that commit could include a backdoor. You have no way of knowing whether this additional commit is "authorized" by the project leads/owners or not.

That is in fact the point, it's decentralized by nature. The entire idea behind git's decentralization is that your version with an additional backdoor is no lesser of a version than any other. You handle that at the pointer or address level i.e. deciding to trust your server.

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#146

Hi HN. I am the co-founder of the project. If you are interested in how the protocol works under the hood, start here: https://docs.radicle.xyz/ Docs are still WIP though.

I'm curious if you (or anyone) had a chance to use Mango (https://github.com/axic/mango) before it was abandoned?

Re: Radicle: Open-Source, Peer-to-Peer, GitHub Alternative

#150

Earlier quoted context omitted.

Repositories and code-sharing are inherently about trust. Even if you personally audit every line of code, you still need to trust that the owner isn't trying to slip one past you. Identity is a key component of trust.

What you say makes sense. But that trust needs to extend to the hosting platform itself, because the platform can manipulate all non-signed data. I don't see how a GitHub profile by itself is trustworthy. You need some additional, external and independent verification that that GitHub profile is really authentic and doesn't contain compromised code. There is nothing stopping me from creating the accounts IggleSniggle…

I mean... yeah, you obviously have to trust someone to vouch for the authenticity of an identity. In the case of Github, that's the platform owner. In the case of a digital signature, that's the root certificate authority.

With that being said, your example feels pretty far off the mark. You might be able to phish using a similar looking identity, but that's completely unrelated to the trustworthiness of the platform. It's not as though you'll manage to somehow phish Github into showing someone else's trustworthy work history on a spoofed identity.

Post reply on HN