Comment by the_other
3 months ago
Reading the intro, I feel like I got a good hint about what this is. It sounded like "local first git for teams, without the hell of sharing patches via email".
I don't know what gitea or forgejo are, so comparisons wouldn't help me.
The other day someone here coined JTPP - "Just the prompt, please", expressing preference for reading the prompt instead of the e-mail/article it produced. The reasons for that are rather obvious, but I think it applies to marketing copy in general.
With that in mind, I wonder what the original idea behind this project was - the "prompt" that someone got in their mind, which got them excited enough to build this. Reading the "original prompt" might make it easier to figure the product out. Marketing copy is "how we can make what we have look more alluring to people". The "original prompt" is directly answering "what we actually aspired to build".
"make a thing that works like github but doesn't need github or email"
I wrote that as a joke but now that I'm reading it... even a terrible prompt might be useful.
Changed "make a thing" to "describe a tool" and got a raft of text back that I couldn't be bothered to think about, because it's not my space. This jumped out though:
"## Existing things that almost do this (but don’t go far enough)
* Radicle – closest philosophically [...]"
So it seems to me that you succinctly described Radicle - at least well enough for an LLM to recognize it.
P2P Github
In case anyone is reading this and is merely looking for "local first git for teams, without the hell of sharing patches via email", the solution to this is to establish an empty repository (git init --bare --shared=group) in any mountable shared storage you have, and then setting that repository as the remote for your local branches.
I can tell you. Forgejo is a git server (i.e. you can push to a remove that lives in a different machine) plus a web GUI that allows to list repos, list commits within a repo, navigate commits and files within a commit.
The license is Free and Copyleft.
You still have to run it on a server somewhere, which Nintendo can get shut down.
Nintendo (or whoever) will shutdown whatever users visit to download the thing they want gone. From a skim through the user guide, Radicle seems to only handle the dev/backend side of things and Nintendo wouldn't care that much about it. After all there are already several git mirrors of Yuzu, what was lost was the official "download this" page and the centralized Github bits (issues, etc), though other projects could like handle this bit just fine either as addons (Forgejo) or natively (like the Fossil SCM).
1 reply →
Nintendo can't shutdown your git server if it's running on a Raspberry Pi in your pantry, or a NAS appliance in your home office/basement.
As a matter of fact, Forgejo/Gitea are excellent choices for automatic mirroring of any Git repos you fear may be shutdown by DMCA shenanigans.
11 replies →