#radicle — Public Fediverse posts

#Radicle is the neatest new tool I've seen a while.

Shame (imo) its in Rustlang (as opposed to Golang, for example.) And I wish I knew their dev contrib policy on AI. (looks like they allow?)

But on paper I love a lot about their features, architecture and style!

#Radicle is the neatest new tool I've seen a while.

Shame (imo) its in Rustlang (as opposed to Golang, for example.) And I wish I knew their dev contrib policy on AI. (looks like they allow?)

But on paper I love a lot about their features, architecture and style!

Ah yes, Radicle: the latest attempt to liberate us from the clutches of centralized code hosting 🤣. Now you too can experience the joy of running a peer-to-peer network in your mom's basement while desperately trying to remember which repository ID corresponds to your "sovereign" project. 🚀💾✨
https://radicle.dev/ #Radicle #PeerToPeer #Decentralization #CodeHosting #OpenSource #Sovereignty #HackerNews #ngated

Ah yes, Radicle: the latest attempt to liberate us from the clutches of centralized code hosting 🤣. Now you too can experience the joy of running a peer-to-peer network in your mom's basement while desperately trying to remember which repository ID corresponds to your "sovereign" project. 🚀💾✨
https://radicle.dev/ #Radicle #PeerToPeer #Decentralization #CodeHosting #OpenSource #Sovereignty #HackerNews #ngated

Ah yes, Radicle: the latest attempt to liberate us from the clutches of centralized code hosting 🤣. Now you too can experience the joy of running a peer-to-peer network in your mom's basement while desperately trying to remember which repository ID corresponds to your "sovereign" project. 🚀💾✨
https://radicle.dev/ #Radicle #PeerToPeer #Decentralization #CodeHosting #OpenSource #Sovereignty #HackerNews #ngated

Ah yes, Radicle: the latest attempt to liberate us from the clutches of centralized code hosting 🤣. Now you too can experience the joy of running a peer-to-peer network in your mom's basement while desperately trying to remember which repository ID corresponds to your "sovereign" project. 🚀💾✨
https://radicle.dev/ #Radicle #PeerToPeer #Decentralization #CodeHosting #OpenSource #Sovereignty #HackerNews #ngated

Ah yes, Radicle: the latest attempt to liberate us from the clutches of centralized code hosting 🤣. Now you too can experience the joy of running a peer-to-peer network in your mom's basement while desperately trying to remember which repository ID corresponds to your "sovereign" project. 🚀💾✨
https://radicle.dev/ #Radicle #PeerToPeer #Decentralization #CodeHosting #OpenSource #Sovereignty #HackerNews #ngated

Radicle: Sovereign {code forge} built on Git

https://radicle.dev/

#HackerNews #Radicle #Sovereign #CodeForge #Git #OpenSource #Decentralization

Radicle: Sovereign {code forge} built on Git

https://radicle.dev/

#HackerNews #Radicle #Sovereign #CodeForge #Git #OpenSource #Decentralization

Radicle: Sovereign {code forge} built on Git

https://radicle.dev/

#HackerNews #Radicle #Sovereign #CodeForge #Git #OpenSource #Decentralization

Radicle: Sovereign {code forge} built on Git

https://radicle.dev/

#HackerNews #Radicle #Sovereign #CodeForge #Git #OpenSource #Decentralization

Radicle: Sovereign {code forge} built on Git

https://radicle.dev/

#HackerNews #Radicle #Sovereign #CodeForge #Git #OpenSource #Decentralization

This says https://rns.recipes/forum/general/re-discontinuing-the-github-mirror #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

This says https://rns.recipes/forum/general/re-discontinuing-the-github-mirror #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

This says https://rns.recipes/forum/general/re-discontinuing-the-github-mirror #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

This says https://rns.recipes/forum/general/re-discontinuing-the-github-mirror #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

This says https://rns.recipes/forum/general/re-discontinuing-the-github-mirror #reticulum code is to be taken off #github or IP based repos. I was not able to join the discussion - was locked. Just wanted to say that github is the reference location for code (a shame, but still fact), and that I am using #radicle as a robust meshed git repo system & #codeberg so no sheep. As mirror repo codeberg/github are ok locations just to get it out & get bootstrapped. To only get the #RNS code over #rngit reticulum itself seem not beginner-friendly.

Weird, pushed a commit as a patch update (amended commit ) to my #radicle ref/patches/xxxx ref and…. the patch got closed/merged. Weird.

Weird, pushed a commit as a patch update (amended commit ) to my #radicle ref/patches/xxxx ref and…. the patch got closed/merged. Weird.

Weird, pushed a commit as a patch update (amended commit ) to my #radicle ref/patches/xxxx ref and…. the patch got closed/merged. Weird.

Weird, pushed a commit as a patch update (amended commit ) to my #radicle ref/patches/xxxx ref and…. the patch got closed/merged. Weird.

Weird, pushed a commit as a patch update (amended commit ) to my #radicle ref/patches/xxxx ref and…. the patch got closed/merged. Weird.

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

Ok. Nach der Entwicklung bei #gitlab sehe ich mich nach Alternativen um. #onedev fällt aus: "Built-in AI for DevOps Intelligence" und "Workspaces for Vibe Coding" - würg! #gogs genauso: ich klicke auf der Startseite auf "features" und lande mitten in der Doku unter "authentication" - brauch ich nicht! #radicle hatte ich mir schon mal angesehen und fand's damals zu kompliziert und sinnlos - neues Protokoll, das alles tut, was #git tut - es nur anders nennt - nee... #gitea - hmm, weiß ich nicht..

@hn100 Wonderful article. Could have been worth mentioning #radicle perhaps (so one would really have to do one's research) @db

@hn100 Wonderful article. Could have been worth mentioning #radicle perhaps (so one would really have to do one's research) @db

@hn100 Wonderful article. Could have been worth mentioning #radicle perhaps (so one would really have to do one's research) @db

@hn100 Wonderful article. Could have been worth mentioning #radicle perhaps (so one would really have to do one's research) @db

@hn100 Wonderful article. Could have been worth mentioning #radicle perhaps (so one would really have to do one's research) @db

I use and love #crev & #vet — instruments for WoT crowd-review and supply-chain protection.

#TIL Tangled. It's like #Radicle. Unfortunately over the git too, but also supports jj, that isn't #pijul but not git.

I also read a very important blog post for me there: "combat LLM spam by building a web of trust" https://blog.tangled.org/vouching/ .

I use and love #crev & #vet — instruments for WoT crowd-review and supply-chain protection.

#TIL Tangled. It's like #Radicle. Unfortunately over the git too, but also supports jj, that isn't #pijul but not git.

I also read a very important blog post for me there: "combat LLM spam by building a web of trust" https://blog.tangled.org/vouching/ .

I use and love #crev & #vet — instruments for WoT crowd-review and supply-chain protection.

#TIL Tangled. It's like #Radicle. Unfortunately over the git too, but also supports jj, that isn't #pijul but not git.

I also read a very important blog post for me there: "combat LLM spam by building a web of trust" https://blog.tangled.org/vouching/ .

I use and love #crev & #vet — instruments for WoT crowd-review and supply-chain protection.

#TIL Tangled. It's like #Radicle. Unfortunately over the git too, but also supports jj, that isn't #pijul but not git.

I also read a very important blog post for me there: "combat LLM spam by building a web of trust" https://blog.tangled.org/vouching/ .

A single-file browser tool for binding Nostr and Radicle identities.

https://tangled.org/metaend.eth.xyz/nsec-to-radicle

#nostr #radicle #privacy

The prolonged attack on #Canonical #ubuntu servers is affecting updates. I’ve been wondering whether a system like #radicle could maybe help as a secondary mirror and reduce the impact of outages or attacks. I mirror my Codeberg repo to a Radicle seed node to cope with #Codeberg outages. That does not mean I can push when Codeberg is down. The single-source-of-truth issue is still unclear to me, but downloading a pre-attack version should be possible. Pushing new work during an attack is tricky.

The prolonged attack on #Canonical #ubuntu servers is affecting updates. I’ve been wondering whether a system like #radicle could maybe help as a secondary mirror and reduce the impact of outages or attacks. I mirror my Codeberg repo to a Radicle seed node to cope with #Codeberg outages. That does not mean I can push when Codeberg is down. The single-source-of-truth issue is still unclear to me, but downloading a pre-attack version should be possible. Pushing new work during an attack is tricky.

The prolonged attack on #Canonical #ubuntu servers is affecting updates. I’ve been wondering whether a system like #radicle could maybe help as a secondary mirror and reduce the impact of outages or attacks. I mirror my Codeberg repo to a Radicle seed node to cope with #Codeberg outages. That does not mean I can push when Codeberg is down. The single-source-of-truth issue is still unclear to me, but downloading a pre-attack version should be possible. Pushing new work during an attack is tricky.

The prolonged attack on #Canonical #ubuntu servers is affecting updates. I’ve been wondering whether a system like #radicle could maybe help as a secondary mirror and reduce the impact of outages or attacks. I mirror my Codeberg repo to a Radicle seed node to cope with #Codeberg outages. That does not mean I can push when Codeberg is down. The single-source-of-truth issue is still unclear to me, but downloading a pre-attack version should be possible. Pushing new work during an attack is tricky.

The prolonged attack on #Canonical #ubuntu servers is affecting updates. I’ve been wondering whether a system like #radicle could maybe help as a secondary mirror and reduce the impact of outages or attacks. I mirror my Codeberg repo to a Radicle seed node to cope with #Codeberg outages. That does not mean I can push when Codeberg is down. The single-source-of-truth issue is still unclear to me, but downloading a pre-attack version should be possible. Pushing new work during an attack is tricky.

This is the foundation for the broader radicle-nostr-bridge concept: publish Radicle activity (repo announcements, patches, issues) as Nostr events for discovery, while keeping the canonical git data on Radicle.

https://tangled.org/metaend.eth.xyz/nsec-to-radicle

#nostr #radicle @radicle

@dbtechyt If #github is/has a problem, as alleged here: https://youtu.be/6FYKxl4SZ_o?is=cz2vUYhQk3jtkuHS then perhaps
#radicle is an option: https://radicle.dev/

@dbtechyt If #github is/has a problem, as alleged here: https://youtu.be/6FYKxl4SZ_o?is=cz2vUYhQk3jtkuHS then perhaps
#radicle is an option: https://radicle.dev/

@dbtechyt If #github is/has a problem, as alleged here: https://youtu.be/6FYKxl4SZ_o?is=cz2vUYhQk3jtkuHS then perhaps
#radicle is an option: https://radicle.dev/

@dbtechyt If #github is/has a problem, as alleged here: https://youtu.be/6FYKxl4SZ_o?is=cz2vUYhQk3jtkuHS then perhaps
#radicle is an option: https://radicle.dev/

@dbtechyt If #github is/has a problem, as alleged here: https://youtu.be/6FYKxl4SZ_o?is=cz2vUYhQk3jtkuHS then perhaps
#radicle is an option: https://radicle.dev/

@halfbyte for a possible technology, I see #radicle. https://radicle.dev/

@halfbyte for a possible technology, I see #radicle. https://radicle.dev/