Commit graph

6 commits

Author SHA1 Message Date
Local Dev
734f6853ef site(ariadne.x, theseus.x): standardise sub-page topnavs; fix relative paths
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.
2026-10-04 18:09:20 +02:00
Local Dev
690d46c125 whitepaper page: diagram label for the Sia name list 2026-10-01 22:28:55 +02:00
Local Dev
ad1ca915bc whitepaper: corrections from a review against the code; trademark note covers every brand kit 2026-10-01 22:28:11 +02:00
Local Dev
a2e7939f99 site(theseus.x): whitepaper without release versions; licensing names the brand kits 2026-10-01 22:07:02 +02:00
Local Dev
6342e298f4 Licenses: MPL-2.0 for Theseus, Ariadne and Hephaestus; Apache-2.0 for Argus; CC BY 4.0 for the documents
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.
2026-09-29 00:18:00 +02:00
Local Dev
823056a664 site(theseus.x): the whitepaper as a page, linked from the nav 2026-09-28 23:37:18 +02:00