by aiw1nt3rs on 9/11/24, 9:40 AM with 65 comments
by bongobingo1 on 9/11/24, 11:03 AM
$ sudo chown $(whoami): /usr/local/{bin,man,man/man1}
Seems kinda weird to chown all that in the install instructions? Or am I the weird one. Edit: This is from the seed guide, the user guide suggests installing to ~/.radicle.Also booo for using ~/.radicle instead of ~/.config|local|whatever.
Some quirks and bumps, but the software is good at first impression. I really hope something like this can take off. Needs a good (and somehow trustable/authoritative) searchable index though as that's 90% of what most users want from Github I think.
I do wonder if the protocol could be adopted into something like Forgejo to aid adoption of the P2P idea.
by boramalper on 9/11/24, 1:33 PM
> ForgeFed is a federation protocol for software forges and code collaboration tools for the software development lifecycle and ecosystem. This includes repository hosting websites, issue trackers, code review applications, and more. ForgeFed provides a common substrate for people to create interoperable code collaboration websites and applications.
It's based on ActivityPub [1], the same protocol that powers Mastodon [2], Lemmy [3], and Pixelfed [4].
by dang on 9/11/24, 11:58 AM
Radicle is an open source, peer-to-peer code collaboration stack built on Git - https://news.ycombinator.com/item?id=40166736 - April 2024 (53 comments)
Radicle: Peer-to-Peer Collaboration with Git - https://news.ycombinator.com/item?id=39868504 - March 2024 (10 comments)
How Radicle Works Under the Hood - https://news.ycombinator.com/item?id=39837117 - March 2024 (16 comments)
Radicle: Sovereign code forge built on Git hits v1.0 - https://news.ycombinator.com/item?id=39829736 - March 2024 (3 comments)
Radicle: Open-Source, Peer-to-Peer, GitHub Alternative - https://news.ycombinator.com/item?id=39600810 - March 2024 (284 comments)
Understanding Peer-to-Peer Git Forges with Radicle - https://news.ycombinator.com/item?id=25322584 - Dec 2020 (14 comments)
Radicle: A peer-to-peer alternative to GitHub - https://news.ycombinator.com/item?id=25313010 - Dec 2020 (255 comments)
Radicle-Link: Extending Git with Peer-to-Peer Network Discovery - https://news.ycombinator.com/item?id=24382589 - Sept 2020 (37 comments)
Show HN: Radicle. A decentralized alternative to GitHub built on IPFS - https://news.ycombinator.com/item?id=19591011 - April 2019 (1 comment)
Radicle Architecture - https://news.ycombinator.com/item?id=19511525 - March 2019 (18 comments)
Radicle: A decentralized alternative to GitHub built on IPFS - https://news.ycombinator.com/item?id=19367916 - March 2019 (82 comments)
by nunobrito on 9/11/24, 11:40 AM
Is support for NOSTR planned on the roadmap?
Because they have hundreds of relays and with one single identity we can combine git and text publications, as well as combine with the rest of the open ecossystem built around NOSTR.
Right now is OK, just that is makes everyone keep separate key accounts and data.
by mg on 9/11/24, 10:38 AM
Project management is done in a plan/ directory which has task entries like
1000-add_logout_button.txt
Where 1000 is the priority.There is also a directory plan/done/ where tasks go that have been completed. In the plan/done/ directory, the priority gets replaced by the completion date, so it looks like this:
2024-09-04-add_logout_button.txt
This has a bunch of nice consequences. Some of them are:Task management does not need any software or logins.
Task management can be done directly in Vim by simply looking into and editing the plan/ directory.
Task history is nicely versioned by git automatically.
All the tooling that comes with bash and git can be used on the plan/ dir. Like finding all tasks that contain the term "rounded corners" in the description is just
grep -r 'rounded corners' plan/
by alphazard on 9/11/24, 12:34 PM
However there are a lot of things that seem more complicated than necessary.
https://radicle.xyz/guides/protocol
I'm reading through the delegate consensus model for branches and I don't see why any of that is necessary. It's encroaching on the P2P that Git already does well, which is who I decide to push and pull from. I think this project could learn a lot from the KeyBase model, which is to just be a transport for Git.
- Nodes in the network should host local Git remotes. In Git you would configure the remote (origin is the conventional default) to be the address of the local Radicle daemon + a public key for the device that owns it + the repository name. Something like `http://localhost:<radicalport>/<device_id>/repository_name`. If the device_id is the local device then it stores the repository internally, otherwise it calls out to the P2P network.
- You can add multiple remotes to a Git repository, so you could have a remote for each copy of the repository on each Radicle device you care to sync with. Git push pull just works.
- You can use the very simple regexp branch protection model that GitHub and friends use on each device. e.g. master in MyRepo on DeviceA only allows pushes from DeviceB. DeviceIDs become the primitive for authentication. Groups of Device IDs become users.
- There is plenty of existing tooling for managing mirroring and syncing on top of Git. What we are missing is a way to securely push and pull between arbitrary devices on the network by cryptographic id. e.g. I'm on my laptop, I want to pull from new-feature4 on my friend's desktop, I know its public key, not its IP address, and I know the branch name, figure it out for me.
- This doesn't mean that the source of truth device has to be online to access the repository. Since there is a single source of truth it can sign any changes, and everyone interested can cache those changes, using the signature to know the refs are legitimate.
by v3ss0n on 9/11/24, 11:55 AM
by udev4096 on 9/11/24, 11:51 AM
That's quite impressive.
by jhvkjhk on 9/11/24, 11:20 AM
by Jnr on 9/11/24, 10:55 AM
It was not clear from the home page what exactly it is and how it works, and I don't really want to read the whole documentation.
For me pesonally Github, Gitlab and Gitea is all about discovery. Their interface is easy to understand, fast to search for repositories and easy to contribute. I am not sure what problem Radicle is solving, other than "reliance on big tech". And it has always been possible to mirror git repos from github and other platforms. You could not mirror issues and CI pipelines, but not sure if Radicle solves that.
by ImHereToVote on 9/11/24, 1:54 PM
by lnenad on 9/11/24, 10:54 AM
by lucideer on 9/11/24, 10:44 AM
This looks really nice & polished - love the web ui - but I know there's a pretty active network & community on SSB.
by amiga386 on 9/11/24, 10:57 AM
by otabdeveloper4 on 9/11/24, 1:01 PM
[The main use case for this software]
by vouaobrasil on 9/11/24, 11:18 AM