We have moved! Our main domain changed from radicle.xyz to radicle.dev. Our handle will remain unchanged for now. Read more at https://radicle.dev/2026/04/23/domain-move
Remote
Radicle
@radicle@toot.radicle.xyz
The sovereign forge. Local-first, peer-to-peer and secure code collaboration.
0 Followers
0 Following
9 Posts
Joined May 03, 2024
website:
twitter:
bluesky:
pronouns:
it/its
Radicle 1.7.0, *Daffodil*, has emerged from the ground, with a whopping 226 commits 📈
⚠️ This release contains a security fix, so please upgrade your nodes ASAP.
👾 Check out our update https://radicle.xyz/2026/03/18/radicle-1.7.0
👾 Get the latest radicle.xyz/download 🌱
We're so back! We're in the new year and we have released 1.6.0 (*Amaryllis*) of the Radicle binaries.
👾 Check out our update https://radicle.xyz/2026/01/14/radicle-1.6.0
👾 Get the latest https://radicle.xyz/download 🌱
This release we have a huge turnout of contributors, big thanks to:
- ade
- icetan
- defelo
- Johannes K.
- matthias
- Richard L.
- Sebastian M.
- Yaroslav H.
The team reacted with blazing speed and incorporated fixes to issues that were introduced in 1.7.0 🔥
Get Radicle 1.7.1 👇
👾 Check out the update https://radicle.xyz/2026/03/20/radicle-1.7.1
👾 Get the latest radicle.xyz/download 🌱
Radicle 1.8.0, Drosera, has been released; quick off the back of our 1.7.0 and 1.7.1 releases.
⚠️ This release contains the previous security fix and downgrade protections, so please upgrade your nodes ASAP.
👾 Check out our update https://radicle.xyz/2026/03/30/radicle-1.8.0
👾 Get the latest radicle.xyz/download 🌱
We have release 1.6.1 to help reduce logging noise that was introduced in 1.6.0
👾 Get it, as per usual, at radicle.xyz/download 🌱
Replying to
@csepp@merveilles.town @jakintosh@merveilles.town If you have Radicle installed properly (rad self is happy, and the push URL you use points at a repo you seed and includes your Node ID), then this should work fine. Ping back if it does not.
Replying to
@csepp@merveilles.town @jakintosh@merveilles.town Use git remote -v for an overview in case you get confused. If you do that in the repo with working rad you will also see the difference in fetch and push URL there.
Replying to
@csepp@merveilles.town @jakintosh@merveilles.town The URL does not "include your Node ID" as mentioned above. Use the URL from the successful output to configure your remote.
The point is that you used the fetch URL for `rad` as a push URL for your multi-push-URL remote. Instead, use the push URL of `rad`.
`git remote set-url --add --push rad://z2…yg/z6Mk…UVue`
Note that you will probably have to remove the other (non-working) URL you have added before.