@stevenroose

@graue @edward

Yes @Codeberg #CodeBerg runs on #forgejo @forgejo - a #Gitea fork - which is working on federation. But if the protocol is established, other non-forgejo forges have to adopt it in their codebase aswell for it to work with codeberg.

#gnu #guix #sourcehut #forgefed #gitea #radicle

@MarkusEicher
You might like #Radicle for decentralised version control network. Under the hood, it uses #Git and a bunch of other open tools for achieving this goal. Last time I checked, they had local-first merge requests in plans. Awesome stuff! :surprised_pikachu:

I believe issues and PRs should be enough for discussing, otherwise maybe Codeberg.

Two decentralized #GitHub alternatives are #git-ssb and #radicle.xyz Anyone tried these? Low adoption could be a big factor here. Just hate to see the censorship on GitHub thus far.

@thelinuxexperiment For hosting code freely, there's always alternatives. I'd like to switch to #radicle and use #dagger for my CI solution.

Is #GiveUpGithub too early? Maybe we need #federation first before breaking up the largest sourceforge into multiple instances of #gitlab, #gitea, #sourcehut, etc.

Or instead of just promoting those, we need a decentralized sourceforge like #radicle

Toot about change SequiaPGP library license lead me to two interesting project worth looking at:

- Pijul - distributed version control system ( https://pijul.org )
- Radicile - decentralized code collaboration network ( https://docs.radicle.xyz

#dvcs #Radicle #Pijul #git

“Hypothetically, a federated GitLab could fill all the requirements, however, federated services cannot be offline-first and don’t offer sovereignty over user's identity. Users are tied to specific instances and thus subject to some of the same drawbacks as centralized services.” ( https://docs.radicle.xyz/docs/understanding-radicle/why-radicle )

I disagree. Having instances with a particular group of peers, codes and culture is the strong point of federation. The #Radicle design shows the flaws of purist free software and purist p2p ideology with an impoverished idea of social interactions. Operating Tor or Bittorrent is the most asocial activity I can imagine. I truly hope #ForgeFed ( https://talk.feneas.org/c/forgefed/10 ) will succeed at some point.

I also don't see why federation means it cannot be offline. There is no reason a federated git client couldn't cache the status and activities. There is a bit too mucher prepper aesthetics here.

So, Ukrainian government have banned github. Should we expect pump of #radicle token? )

Le problème de plate-formes comme #GitHub ou #GitLab c'est l'hébergement, où sont hébergées les données ?

Voici une solution, en peer-to-peer ! #Radicle !

https://radicle.xyz/

Great article on #radicle

Understanding Peer-to-Peer Git Forges with Radicle

"The peer creates a local git repository called the __monorepo__ for the purpose of storing portions of the global namespace."

"We can publish identities that we track in `remotes/`. It's a recursive refs layout. This is how someone tracking our refs can find out about related identities and their refs."

http://blog.vmsplice.net/2020/12/understanding-peer-to-peer-git-forges.html

A decentralized alternative to #github with #git collaboration: #Radicle. Very interested in this! https://docs.radicle.xyz/docs/what-is-radicle

#Radicle – Le #Github décentralisé
https://tinyurl.com/y5fdnkw5