| + |
---
|
| + |
title: "We have moved to radicle.{dev,network}!"
|
| + |
image: radicle-1.png
|
| + |
---
|
| + |
|
| + |
We have moved! Our main domain changed from [radicle.xyz] to [radicle.dev], because we wanted to be closer to our main audience of software developers. In addition, we use this occasion to implement another change, with a more technical motivation.
|
| + |
|
| + |
Back in 2025-10, we received multiple reports that our domain, radicle.xyz, did not resolve via the ISPs Swisscom, Telenor, and Virgin Media. The domain was indexed and added to various block lists. Unfortunately, the keepers of these block lists are not very open about their reasons for blocking, so we do not know exactly why radicle.xyz was indexed. We believe that the reason was content served via app.radicle.xyz, our public instance of Radicle Explorer, which allows you to access many nodes in the network. (Note that most of these block lists do not differentiate subdomains, but have exceptions for cases like co.uk.)
|
| + |
|
| + |
Since that incident, we were looking for ways to protect ourselves from getting blocked again in the future. The obvious way would be to self-censor, and have app.radicle.xyz only serve curated content. Obviously we reject this approach, because we want to host an instance of Radicle Explorer to provide a view onto as many repositories as possible, with as little discrimination/censorship as possible. (Please note that we have blocked nodes and repositories on iris.radicle.xyz and rosa.radicle.xyz in the past, if we felt that they were clearly overstepping boundaries, and we will continue to do so. If anyone thinks that this undermines the censorship resistance of Radicle, please think again.)
|
| + |
|
| + |
Rather, the mitigation that we found more appealing, was to use a different domain, and separate content out accordingly. This means that, going forward, we will split:
|
| + |
1. Content *about* Radicle (explainers, guides, download links, blog posts) which is under control of the Radicle team. We will use radicle.dev for these purposes.
|
| + |
2. Content *on* Radicle (repositories hosted on practically any node on the network) which the Radicle team has only very little control over, accessible via Radicle Explorer. Going forward, our deployment of Radicle Explorer will *not* be hosted on app.radicle.xyz anymore, but instead it will be hosted at [radicle.network].
|
| + |
|
| + |
The idea is of course that if there are complaints about or issues with radicle.network in the future, we hope that radicle.dev stays largely unaffected and people can continue to inform themselves about Radicle and learn how to set it up.
|
| + |
|
| + |
We will, for the foreseeable future, serve redirects from app.radicle.xyz to radicle.network, so that your links do not break, but please make the switch soon.
|
| + |
|
| + |
Our permissive seed nodes Iris and Rosa should now be addressed as iris.radicle.network and rosa.radicle.network, and the next release of Radicle will include an appropriate change. Note that they also will keep responding to iris.radicle.xyz and rosa.radicle.xyz for some time to ensure a smooth transition. The (non-permissive) seed node that the team uses for development was renamed to seed.radicle.dev.
|
| + |
|
| + |
Our AT Protocol handle changed to radicle.dev. On Mastodon, to not impact federation, we will stay on toot.radicle.xyz for now, but may move to another instance soon.
|
| + |
|
| + |
[radicle.xyz]: https://radicle.xyz
|
| + |
[radicle.dev]: https://radicle.dev
|
| + |
[radicle.network]: https://radicle.network
|