See Drips on https://docs.radworks.org/#projects
I'd first heard of Radicle from this post: https://blog.orhun.dev/open-source-funding-with-ratatui/
[0]: https://news.ycombinator.com/item?id=39600810 [1]: https://news.ycombinator.com/item?id=39837117 [2]: https://news.ycombinator.com/item?id=39868504
Perhaps in the future, a user could use a web interface for a Radicle node and they post it directly from their browser. Some questions about that would the verifiability of that action though. Definitely some food for thought here!
Sometimes yes, sometimes no.
Sometimes they flip out about GitHub and go on Reddit instead and write something like this: https://www.reddit.com/r/github/comments/1at9br4/i_am_new_to...
But then again my username is all non-software engineers :shrug:
Everyone can already self-host Gitea or Gitlab, and Git repos are super easy to clone, so what’s the point of all the peer to peer stuff?
ie. what real world problem is it supposed to solve?
Ah, that’s not that much of a problem these days, where password managers (and failing that, SSO with Facebook/Google/etc.) has become wide-spread.
And unless everyone moved to Radicle, it’s just one more system you need to track authentication info for.
You may notice that the title is "peer-to-peer code collaboration stack built on Git", emphasis on "built on". We're using Git as a storage and transport mechanism for code collaboration data. So we're building a local-first tool for the social data, e.g. patches and issues.
Everyone knows Linus invented and "specifically designed" git as a drop-in tool for his existing email-patch-based kernel development workflow, which is not how 99.9% of the rest of the world prefers to operate these days.
Ideally, we would have a solution to collaborate on projects peer-to-peer that handles some basic Github-style stuff without having to use Github at all.
I’m sure this project brings something new to the table but they’d need a better elevator pitch than “peer-to-peer” to explain that.
> ie. what real world problem is it supposed to solve?
Seems pretty clear from the submitted page.
Problem: centralized code hosting platforms [...] single entity(ies) controlling the network(s)
Solution: Repositories are replicated across peers in a decentralized manner, and users are in full control of their data and workflow.
Literally the first paragraph on the page.
But self-hosting limits exposure, that Github.com/Gitlab.com provide.
>Git repos are super easy to clone
Git is meant to version your code, not issues, pull requests, etc.
https://radicle.xyz/guides/protocol#introduction
This provides comparison and reasoning.
having to self-host anything?
If you're trying to launch a product though, it's something to keep in mind.
Anyways, a good introduction to git-ssb would be this document: https://github.com/hackergrrl/git-ssb-intro
Nodes on the Radicle network subscribe to repository data they are interested in, and peers announce updates that in turn trigger fetches for the underlying content. Just like SSB and Lightning, updates are gossiped on the network until they reach all interested peers."
