explorer: Allow passing seed and base as arguments

Also take a default value from configuration.

Fix all usages and change some hardcoded links to use the filter.

_config.yml

@@ -34,6 +34,7 @@ title: "Radicle: the sovereign forge"
 description: "The Radicle forge is an open source, peer-to-peer code collaboration stack built on Git."
 fedi: "@radicle@toot.radicle.xyz"
 node: "seed.radicle.xyz"
+explorer: "radicle.network"
 atproto: radicle.xyz
 
 # jekyll-feed configuration

_guides/protocol.md

@@ -829,8 +829,8 @@ collaboration.
 [git-v2]: https://git-scm.com/docs/protocol-v2
 [Tor]: https://torproject.org/
 [Ed25519]: https://ed25519.cr.yp.to/
-[iris.radicle.xyz]: {{ "iris.radicle.xyz " | explore }}
-[rosa.radicle.xyz]: {{ "rosa.radicle.xyz " | explore }}
+[iris.radicle.xyz]: {{ "" | explore: "iris.radicle.xyz" }}
+[rosa.radicle.xyz]: {{ "" | explore: "rosa.radicle.xyz" }}
 [reverse-dns]: https://en.wikipedia.org/wiki/Reverse_domain_name_notation
 [tuf]: https://theupdateframework.github.io/specification/latest/
 [noise]: http://www.noiseprotocol.org/noise.html

_guides/seeder.md

@@ -559,7 +559,7 @@ You can query the API with `curl` to ensure everything is working properly:
 ### Adding support for HTTPS
 
 For your HTTP Daemon to be accessible from a frontend such as
-<https://app.radicle.xyz>, it needs to respond to HTTPS requests. To do this,
+<https://{{ site.explorer }}>, it needs to respond to HTTPS requests. To do this,
 we recommend using [Caddy][caddy].
 
 Start by installing `caddy`; most Linux distributions have a package you can
@@ -609,7 +609,7 @@ seed's domain:
     curl https://seed.radicle.example/api/v1
 
 You should now be able to visit your seed node via any Radicle web frontend as
-well. For example, <https://app.radicle.xyz/nodes/seed.radicle.example>.
+well. For example, <https://{{ site.explorer }}/nodes/seed.radicle.example>.
 
 > On some distributions, installing `caddy` will start the system service
 > automatically. If you're not able to connect to your HTTP daemon from the

_layouts/blog.html

@@ -21,7 +21,7 @@
       <h1>{{ page.title }}</h1>
       <p class="subtitle">{{ page.subtitle }}</p>
       <span class="author">
-	      Published by <a href="https://app.radicle.xyz/nodes/{{author.radicle.node | default: site.node }}/users/{{author.radicle.did}}">{{author.name}}</a>
+	      Published by <a href="{{ author.radicle.node | default: site.node | append: ' users/' | append: author.radicle.did | explore }}">{{author.name}}</a>
 	{% if author.atproto %}<a href="{{ author.atproto | prepend: "https://bsky.app/profile/" }}">🦋</a>{% endif %}
 	{% if author.fedi %}<a href="{{ author.fedi | fedi_to_https }}">🐘</a>{% endif %}
 	{% if author.web %}<a href="https://{{ author.web }}">🌐</a>{% endif %}

_plugins/explorer.rb

@@ -1,12 +1,15 @@
 module Jekyll
   module Explorer
-    def explore(input)
-      base = "https://radicle.network/nodes"
-      if input.include?(' ')
-        prefix, suffix = input.split(' ', 2)
-        "#{base}/#{prefix}/#{suffix}"
+    def explore(
+      input,
+      node = @context.registers[:site].config['node'],
+      explorer = @context.registers[:site].config['explorer']
+    )
+      base = "https://#{explorer}"
+      if input.nil?
+        base
       else
-        "#{base}/iris.radicle.xyz/#{input}"
+        "#{base}/nodes/#{node}/#{input}"
       end
     end
   end

_posts/2025-06-13-radicle-desktop.md

@@ -21,7 +21,7 @@ Radicle Desktop is a graphical interface built to simplify some of the more comp
 
 ## What Radicle Desktop (currently) is not
 
-Radicle Desktop is not trying to replace your terminal, IDE, or code editor - you already have your preferred tools for code browsing. It won’t replace our existing [app.radicle.xyz](https://app.radicle.xyz) and [search.radicle.xyz](https://search.radicle.xyz) for finding and exploring projects. It also doesn’t run a node for you. Instead, it communicates with your existing Radicle node, supporting your current workflow and encourages gradual adoption.
+Radicle Desktop is not trying to replace your terminal, IDE, or code editor - you already have your preferred tools for code browsing. It won’t replace our existing [{{ site.explorer }}](https://{{ site.explorer }}) and [search.radicle.xyz](https://search.radicle.xyz) for finding and exploring projects. It also doesn’t run a node for you. Instead, it communicates with your existing Radicle node, supporting your current workflow and encourages gradual adoption.
 
 ## Why we’re excited 🎊
 

_posts/2025-07-23-using-radicle-ci-for-development.md

@@ -47,7 +47,7 @@ I have written a CI engine for myself,
 There are adapters for running CI locally on the host or in a
 container, GitHub actions, Woodpecker, and several others. See [`CI
 broker
-README.md`]({{ "radicle.liw.fi rad:zwTxygwuz5LDGBq255RA2CbNGrz8/tree/README.md" | explore }})
+README.md`]({{ "rad:zwTxygwuz5LDGBq255RA2CbNGrz8/tree/README.md" | explore: "radicle.liw.fi" }})
 and [integration
 documentation](https://explorer.radicle.gr/nodes/seed.radicle.gr/rad:z4Uh671FzoooaHjLvmtW9BtGMF9qm)
 for a more complete list. The adapter interface is intentionally easy
@@ -182,7 +182,7 @@ To push changes, run `git push`.
 There you go. I now have a Radicle repository to play with. As of
 publishing this blog post, the repository is alive on the Radicle
 network, if you want to [look at
-it]({{ "radicle.liw.fi rad:z3dhWQMH8J6nX3Qo97o5oSFMTfgyr" | explore }})
+it]({{ "rad:z3dhWQMH8J6nX3Qo97o5oSFMTfgyr" | explore: "radicle.liw.fi" }})
 or clone it.
 
 # CI configuration in the repository
@@ -212,7 +212,7 @@ I find the most frustrating part of using CI to be to wait for a CI
 run to finish on a server and then try to deduce from the run log what
 went wrong. I've alleviated this by writing an extension to `rad` to
 run CI locally:
-[`rad-ci`]({{ "radicle.liw.fi rad:z6QuhJTtgFCZGyQZhRMZmZKJ3SVG" | explore }}).
+[`rad-ci`]({{ "rad:z6QuhJTtgFCZGyQZhRMZmZKJ3SVG" | explore: "radicle.liw.fi" }}).
 It can produce a huge amount of output, so I've abbreviated that
 below.
 
@@ -481,7 +481,7 @@ but not other systems, since I only use Debian. I would very much
 appreciate help with expanding that documentation.
 
 It's probably easiest to install
-[`rad-ci`]({{ "radicle.liw.fi rad:z6QuhJTtgFCZGyQZhRMZmZKJ3SVG" | explore }})
+[`rad-ci`]({{ "rad:z6QuhJTtgFCZGyQZhRMZmZKJ3SVG" | explore: "radicle.liw.fi" }})
 from source code or with `cargo install`, but I have a `deb` package
 for those using Debian or derivatives in my [APT
 repository](http://apt.liw.fi/).

_posts/2026-03-18-radicle-1.7.0.md

@@ -3,7 +3,7 @@ title: "Radicle 1.7.0 – Daffodil"
 image: radicle-1.png
 ---
 
-[748ddad]: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/748ddade2feb6f00245c2ba878bd54842dc57506
+[748ddad]: {{ "rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/748ddade2feb6f00245c2ba878bd54842dc57506" | explore }}
 
 Spring has sprung, where we're writing from, and Daffodils are in season!
 
@@ -37,7 +37,7 @@ We have taken the time to scan all existing repositories on our public seeds, an
 
 ### Improved `rad/sigrefs`
 
-[`989edacd564fa658358f5ccfd08c243c5ebd8cda`]: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad%3Az3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/989edacd564fa658358f5ccfd08c243c5ebd8cda
+[`989edacd564fa658358f5ccfd08c243c5ebd8cda`]: {{ "rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/989edacd564fa658358f5ccfd08c243c5ebd8cda" | explore }}
 
 The "Signed References" feature was reimplemented.
 The commits in `refs/rad/sigrefs` will now only verify if they carry an appropriate value for `refs/rad/root` in the associated `refs` blob.

_posts/2026-03-20-radicle-1.7.1.md

@@ -3,7 +3,7 @@ title: "Radicle 1.7.1"
 image: radicle-1.png
 ---
 
-[`d9915d2`]: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/d9915d275fd07d20db08cf7d3488f8650e66b88a
+[`d9915d2`]: {{ "rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/d9915d275fd07d20db08cf7d3488f8650e66b88a" | explore }}
 
 The Radicle team would like to announce the release of Radicle 1.7.1 ([`d9915d2`]).
 After releasing [1.7.0]({% post_url 2026-03-18-radicle-1.7.0 %}), our users reported issues after upgrading.
@@ -21,7 +21,7 @@ Partially undo this change to stay backward compatible, but log a warning in cas
 
 ### Signed References compatibility
 
-[`d3bc868e84c334f113806df1737f52cc57c5453d`]: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/d3bc868e84c334f113806df1737f52cc57c5453d
+[`d3bc868e84c334f113806df1737f52cc57c5453d`]: {{ "rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/d3bc868e84c334f113806df1737f52cc57c5453d" | explore }}
 
 In commit [`d3bc868e84c334f113806df1737f52cc57c5453d`] which was released in version 1.7.0, the criteria for verification of Signed References was changed to be more strict.
 In particular, to require the reference `refs/rad/root` pointing at the root commit in the history of the repository identity.

_posts/2026-03-30-disclosure-of-vulnerability-in-signed-references.md

@@ -891,4 +891,4 @@ Acknowledgements: We would like to thank maninak and rudolfs for their helpful c
 [Collaborative Objects]: https://radicle.xyz/guides/protocol#collaborative-objects
 [signed pushes]: https://people.kernel.org/monsieuricon/signed-git-pushes
 [push certificates]: https://git-scm.com/docs/pack-protocol#_push_certificate
-[`rad:z3zzcqqBGP1NdvvMbSDt2jYYp9jSB`]: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3zzcqqBGP1NdvvMbSDt2jYYp9jSB
+[`rad:z3zzcqqBGP1NdvvMbSDt2jYYp9jSB`]: {{ "rad:z3zzcqqBGP1NdvvMbSDt2jYYp9jSB" | explore }}

_posts/2026-03-30-radicle-1.8.0.md

@@ -3,7 +3,7 @@ title: "Radicle 1.8.0 – Drosera"
 image: radicle-1.png
 ---
 
-[46f4c0f]: https://app.radicle.xyz/nodes/seed.radicle.xyz/rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/46f4c0f38ffb181f6e5787997c6153f18ab22902
+[46f4c0f]: {{ "rad:z3gqcJUoA1n9HaHKufZs5FCSGazv5/commits/46f4c0f38ffb181f6e5787997c6153f18ab22902" | explore }}
 [Drosera]: https://en.wikipedia.org/wiki/Drosera
 
 The Radicle team are back sooner than later for this important release, Radicle 1.8.0, code name *[Drosera]*.