The Sirius.X / Theseus.X / Ariadne.X / Hephaestus.X links in the family
topnavs and body copy were written as full https URLs — href="https://sirius.x/".
In Theseus's own browser (where the current page is served over the bns://
scheme) that absolute URL triggers the gateway-fallback path on top of the
current host, producing URLs like bns://theseus.x/bns/sirius.x/ that then
accumulate segments as the user clicks around.
Switched 56 cross-family link hrefs to protocol-relative (href="//sirius.x/"
etc.). Protocol-relative URLs inherit the scheme of the current page, so:
- In Theseus on bns://theseus.x/ the link resolves to bns://sirius.x/ —
direct BCNR, no gateway rewrite, no URL accumulation.
- On the silentmode.st ICANN mirror it resolves to https://sirius.x/ —
unchanged from the previous behaviour.
Only the four sibling .X hosts were swapped; silentmode.st, dl.silentmode.st,
code.silentmode.st, navigate.st, and every forge or API URL still carry
their explicit scheme.
Two bugs the user hit while browsing the dev docs:
1. ariadne.x/dev/ used root-style hrefs ("thread", "dev", "assets/…") that
assumed the <base> tag workaround was active. On a client that walks
relative URLs against the page URL (BCNR direct hosts, Theseus in
gateway mode), every click appended one more segment — "/dev/plug-ins",
"/dev/plug-ins/extensions", etc. — because "plug-ins" resolved against
"/dev/" instead of the site root. Switched the dev page to proper "../"
relative paths (../thread/, ../assets/favicon.svg, ../#download) so it
resolves correctly regardless of host or base-tag presence. Same fix
on ariadne.x/thread/ (brand href="" went nowhere; the Product column
pointed every link at the current directory).
2. Theseus sub-pages had drifted apart. The home topnav was already
trimmed to Plug-ins · Extensions · Developers · Sirius.X · Get Theseus,
but plug-ins/, extensions/, brand/, and whitepaper/ still carried the
old "Brand" link in their topnav, had no "Developers" entry at all,
and lacked the mobile hamburger. Standardised all four to the home
pattern and dropped Brand + Whitepaper from the topnav on each page.
Both pages still exist and are reachable from the footer; neither is
on the top-level nav path.
Also added a Developers link + hamburger to ariadne.x/thread/ so the
Ariadne family matches the Theseus family on every page.
The public repos carried no license, so nobody could legally copy or build
on the code, and the whitepaper's "free software" had nothing behind it.
Theseus and its companions take the Mozilla Public License 2.0, the
file-level copyleft Firefox and Brave use, which is compatible with every
component they bundle. The resolver and gateway libraries take Apache-2.0
so that other implementations of the registry can reuse them without
copyleft in the way. The protocol documents and the whitepaper are CC BY 4.0.
A third-party notices file lists what the browser ships and fetches, with
the source offer the GPL sing-box binary the VPN add-on downloads requires;
the matching source archive is now published beside the binaries. The
names and marks are reserved in TRADEMARKS.md, separate from the code
license, so a fork must ship under its own name. Settings › General says
the license and links the three files; the whitepaper says the same.
