silentmode/theseus-site
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
theseus-site/extensions/index.html

489 lines
32 KiB
HTML
Raw Normal View History

feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>theseus.x — Extensions</title>
<meta name="description" content="Signed over-the-air update endpoint for Theseus's bundled add-ons. Each entry is Ed25519-signed by the Silent Mode operator; verified on every install without waiting for a Theseus release.">
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
<link rel="icon" href="../assets/favicon.svg" type="image/svg+xml">
<link rel="mask-icon" href="../assets/favicon.svg" color="#d6ff3d">
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<meta property="og:type" content="website">
<meta property="og:site_name" content="theseus.x">
<meta property="og:title" content="theseus.x — Extensions">
<meta property="og:description" content="Signed OTA update endpoint for Theseus's bundled add-ons. Ed25519, no cert authority, no app-store gatekeeper.">
<meta property="og:url" content="https://theseus.x/extensions/">
<style>
:root{
--bg:#0b0e14; --panel:#141a24; --panel2:#18202c; --line:rgba(255,255,255,.09);
--ink:#e7eaf1; --mut:#8b98a9; --dim:#5e6678; --acid:#d6ff3d;
--ok:#4fd1a5;
}
*{box-sizing:border-box}
body{margin:0;background:radial-gradient(1100px 560px at 50% -12%,#16202e,var(--bg));
color:var(--ink);font:16px/1.65 system-ui,-apple-system,Segoe UI,Roboto,sans-serif;min-height:100vh}
a{color:var(--acid)}
.wrap{max-width:900px;margin:0 auto;padding:0 1.2rem}
site-theseus-x: full-width topnav, Sirius.X tab icon Sidebar was drawing above the topnav border line — the sticky topnav only spanned the content column, so where the sidebar met it a T-shape break was visible. Topnav is now position:fixed spanning the full page width, and the sidebar is anchored to var(--tn-h)=52px so it sits cleanly below the topnav border on all breakpoints. Also: the sirius.x tab is now capitalised Sirius.X and carries its own brand mark (the 4-point sparkle from sirius.x's own favicon) so the tabs read as three named things — Home, Plug-ins, Extensions, Sirius.X — not one lowercase outlier. A shared .topnav a .g rule paints the .X suffix acid green.
2026-09-20 16:17:08 +02:00
.topnav{position:fixed;top:0;left:0;right:0;z-index:20;display:flex;gap:2px;align-items:center;flex-wrap:wrap;
sites: drop the divider line under topnav; fix Sirius .X space theseus.x, sirius.x and hephaestus.x had a 1px border-bottom under the sticky/fixed topnav that read as a visible separator between the navigation and the page. The topnav's own translucent-blur backdrop is enough of a distinction already — the line is redundant and, on the theseus.x sidebar layout, made the top of the sidebar look like it was overhanging the header. theseus.x tabs also had a "Sirius .X" gap because the topnav <a> is a flex container and the icon + "Sirius" text + ".X" span were three flex items with a 6px gap between each. Wrapping the label in one <span> collapses the gap to a single space between icon and label. Sidebar border-right and mobile bottom-bar border-top also dropped — the panel tint carries the boundary; a hard line was too heavy.
2026-09-20 16:33:58 +02:00
padding:10px 1.2rem;background:rgba(11,14,20,.88);backdrop-filter:blur(10px)}
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
.topnav .brand{font-weight:600;color:var(--ink);text-decoration:none;margin-right:14px;font-size:15px;letter-spacing:.2px;display:flex;align-items:center;gap:8px}
.topnav .brand .g{color:var(--acid)}
.topnav .brand svg{width:20px;height:20px}
site-theseus-x: full-width topnav, Sirius.X tab icon Sidebar was drawing above the topnav border line — the sticky topnav only spanned the content column, so where the sidebar met it a T-shape break was visible. Topnav is now position:fixed spanning the full page width, and the sidebar is anchored to var(--tn-h)=52px so it sits cleanly below the topnav border on all breakpoints. Also: the sirius.x tab is now capitalised Sirius.X and carries its own brand mark (the 4-point sparkle from sirius.x's own favicon) so the tabs read as three named things — Home, Plug-ins, Extensions, Sirius.X — not one lowercase outlier. A shared .topnav a .g rule paints the .X suffix acid green.
2026-09-20 16:17:08 +02:00
.topnav a{color:var(--mut);text-decoration:none;padding:6px 12px;border-radius:8px;font-size:14px;
display:inline-flex;align-items:center;gap:6px}
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
.topnav a:hover{color:var(--ink);background:var(--panel)}
.topnav a.here{color:var(--acid);background:rgba(214,255,61,.08)}
site-theseus-x: full-width topnav, Sirius.X tab icon Sidebar was drawing above the topnav border line — the sticky topnav only spanned the content column, so where the sidebar met it a T-shape break was visible. Topnav is now position:fixed spanning the full page width, and the sidebar is anchored to var(--tn-h)=52px so it sits cleanly below the topnav border on all breakpoints. Also: the sirius.x tab is now capitalised Sirius.X and carries its own brand mark (the 4-point sparkle from sirius.x's own favicon) so the tabs read as three named things — Home, Plug-ins, Extensions, Sirius.X — not one lowercase outlier. A shared .topnav a .g rule paints the .X suffix acid green.
2026-09-20 16:17:08 +02:00
.topnav a .g{color:var(--acid)}
.topnav a svg.tabicon{width:15px;height:15px;flex:none}
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
/* Mobile hamburger — matches the home-page pattern. */
.topnav .menu{display:none}
@media (max-width:720px){
.topnav{flex-wrap:nowrap;padding:10px 1rem}
.topnav .brand{margin-right:0}
.topnav > a:not(.brand){display:none}
.topnav .menu{display:block;margin-left:auto;position:relative}
.topnav .menu > summary{list-style:none;cursor:pointer;padding:8px 10px;
border-radius:8px;color:var(--mut);display:inline-flex;align-items:center;gap:6px}
.topnav .menu > summary::-webkit-details-marker{display:none}
.topnav .menu > summary svg{width:22px;height:22px;display:block}
.topnav .menu > summary:hover,
.topnav .menu[open] > summary{color:var(--ink);background:var(--panel)}
.topnav .menu .menu-panel{position:absolute;top:calc(100% + 6px);right:0;
background:var(--bg);border:1px solid var(--line);border-radius:12px;
padding:6px;min-width:220px;display:flex;flex-direction:column;gap:2px;
box-shadow:0 10px 32px rgba(0,0,0,.55)}
.topnav .menu .menu-panel a{padding:10px 14px;border-radius:8px;font-size:14.5px;
color:var(--mut);text-decoration:none;display:flex;align-items:center;gap:8px}
.topnav .menu .menu-panel a:hover{color:var(--ink);background:var(--panel)}
}
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
.topnav a.get{margin-left:auto;background:rgba(214,255,61,.10);color:var(--acid);font-weight:500}
.topnav a.get:hover{background:rgba(214,255,61,.18)}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
/* Adaptive edge nav: full-width panel at left edge on wide,
icon rail on medium, bottom bar with icons on mobile. */
site-theseus-x: overlay sidebar so content stays centred; sirius.x: Theseus.X The sidebar's body padding-left was pushing the whole page — hero, cards, footer — to the right of centre, off the axis of the hero title. Removed the body reserve; the sidebar is now a pointer-events:none overlay on top of the page. Content wraps back to the middle of the viewport regardless of sidebar width. Links float at opacity 0.35 by default so the sidebar reads as chrome rather than a panel — the section text underneath stays legible. On hover a link snaps to full opacity, picks up an ink colour and a subtle blurred backdrop so it doesn't compete with the content. The active-section link keeps the acid tint at 0.85 and finishes to 1 on hover. Icon rail and mobile bar unchanged. Sirius.X: the Theseus tab link in the topnav now reads Theseus.X with the .X in acid green, matching the naming everywhere else in the ecosystem.
2026-09-20 17:46:55 +02:00
:root{--sn-w:200px;--tn-h:52px}
body{padding-top:var(--tn-h)}
site-theseus-x: full-width topnav, Sirius.X tab icon Sidebar was drawing above the topnav border line — the sticky topnav only spanned the content column, so where the sidebar met it a T-shape break was visible. Topnav is now position:fixed spanning the full page width, and the sidebar is anchored to var(--tn-h)=52px so it sits cleanly below the topnav border on all breakpoints. Also: the sirius.x tab is now capitalised Sirius.X and carries its own brand mark (the 4-point sparkle from sirius.x's own favicon) so the tabs read as three named things — Home, Plug-ins, Extensions, Sirius.X — not one lowercase outlier. A shared .topnav a .g rule paints the .X suffix acid green.
2026-09-20 16:17:08 +02:00
.sidenav{position:fixed;top:var(--tn-h);left:0;bottom:0;width:var(--sn-w);z-index:15;
site-theseus-x: overlay sidebar so content stays centred; sirius.x: Theseus.X The sidebar's body padding-left was pushing the whole page — hero, cards, footer — to the right of centre, off the axis of the hero title. Removed the body reserve; the sidebar is now a pointer-events:none overlay on top of the page. Content wraps back to the middle of the viewport regardless of sidebar width. Links float at opacity 0.35 by default so the sidebar reads as chrome rather than a panel — the section text underneath stays legible. On hover a link snaps to full opacity, picks up an ink colour and a subtle blurred backdrop so it doesn't compete with the content. The active-section link keeps the acid tint at 0.85 and finishes to 1 on hover. Icon rail and mobile bar unchanged. Sirius.X: the Theseus tab link in the topnav now reads Theseus.X with the .X in acid green, matching the naming everywhere else in the ecosystem.
2026-09-20 17:46:55 +02:00
background:transparent;padding:56px 12px 22px 18px;
overflow-y:auto;transition:width .15s ease;pointer-events:none}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
.sidenav a{display:flex;align-items:center;gap:14px;color:var(--mut);text-decoration:none;
site-theseus-x: overlay sidebar so content stays centred; sirius.x: Theseus.X The sidebar's body padding-left was pushing the whole page — hero, cards, footer — to the right of centre, off the axis of the hero title. Removed the body reserve; the sidebar is now a pointer-events:none overlay on top of the page. Content wraps back to the middle of the viewport regardless of sidebar width. Links float at opacity 0.35 by default so the sidebar reads as chrome rather than a panel — the section text underneath stays legible. On hover a link snaps to full opacity, picks up an ink colour and a subtle blurred backdrop so it doesn't compete with the content. The active-section link keeps the acid tint at 0.85 and finishes to 1 on hover. Icon rail and mobile bar unchanged. Sirius.X: the Theseus tab link in the topnav now reads Theseus.X with the .X in acid green, matching the naming everywhere else in the ecosystem.
2026-09-20 17:46:55 +02:00
padding:9px 12px;border-radius:10px;
font-size:14.5px;font-weight:500;opacity:.35;pointer-events:auto;
transition:opacity .12s,color .12s,background .12s,backdrop-filter .12s}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
.sidenav a .ic{flex:none;width:22px;font-size:18px;line-height:1;text-align:center;
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
display:none;justify-content:center;align-items:center}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
.sidenav a .lb{flex:1;white-space:nowrap;overflow:hidden;text-overflow:ellipsis}
site-theseus-x: overlay sidebar so content stays centred; sirius.x: Theseus.X The sidebar's body padding-left was pushing the whole page — hero, cards, footer — to the right of centre, off the axis of the hero title. Removed the body reserve; the sidebar is now a pointer-events:none overlay on top of the page. Content wraps back to the middle of the viewport regardless of sidebar width. Links float at opacity 0.35 by default so the sidebar reads as chrome rather than a panel — the section text underneath stays legible. On hover a link snaps to full opacity, picks up an ink colour and a subtle blurred backdrop so it doesn't compete with the content. The active-section link keeps the acid tint at 0.85 and finishes to 1 on hover. Icon rail and mobile bar unchanged. Sirius.X: the Theseus tab link in the topnav now reads Theseus.X with the .X in acid green, matching the naming everywhere else in the ecosystem.
2026-09-20 17:46:55 +02:00
.sidenav a:hover{opacity:1;color:var(--ink);background:rgba(11,14,20,.72);backdrop-filter:blur(8px)}
.sidenav a.active{opacity:.85;color:var(--acid)}
.sidenav a.active:hover{opacity:1}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
@media (max-width:1180px){
:root{--sn-w:64px}
site-theseus-x: full-width topnav, Sirius.X tab icon Sidebar was drawing above the topnav border line — the sticky topnav only spanned the content column, so where the sidebar met it a T-shape break was visible. Topnav is now position:fixed spanning the full page width, and the sidebar is anchored to var(--tn-h)=52px so it sits cleanly below the topnav border on all breakpoints. Also: the sirius.x tab is now capitalised Sirius.X and carries its own brand mark (the 4-point sparkle from sirius.x's own favicon) so the tabs read as three named things — Home, Plug-ins, Extensions, Sirius.X — not one lowercase outlier. A shared .topnav a .g rule paints the .X suffix acid green.
2026-09-20 16:17:08 +02:00
.sidenav{padding:22px 6px}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
.sidenav .lbl{display:none}
.sidenav a{justify-content:center;padding:12px 4px;gap:0}
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
.sidenav a .ic{display:inline-flex}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
.sidenav a .lb{display:none}
}
@media (max-width:720px){
:root{--sn-w:0px}
body{padding-left:0;padding-bottom:64px}
.sidenav{top:auto;bottom:0;left:0;right:0;width:100%;height:auto;
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
padding:4px 4px;flex-direction:row;background:rgba(11,14,20,.52);
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
display:flex;justify-content:space-around;overflow-x:auto}
.sidenav .lbl{display:none}
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
.sidenav a{flex:1;min-width:56px;padding:10px 6px;justify-content:center;gap:0}
.sidenav a .ic{display:inline-flex}
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
.sidenav a .lb{display:none}
}
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
header.hero{text-align:center;padding:3.5rem 1.2rem 1rem}
h1{font-size:clamp(1.8rem,4.5vw,2.4rem);margin:.6rem 0 .3rem;letter-spacing:-.3px}
h1 .g{color:var(--acid)}
.tag{color:var(--mut);font-size:1.02rem;max-width:640px;margin:0 auto}
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
section{padding:2rem 0;border-top:1px solid var(--line);margin-top:1.6rem;scroll-margin-top:72px}
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
section:first-of-type{border-top:none;margin-top:1rem}
h2{font-size:1.35rem;margin:0 0 .5rem}
.lede{color:var(--mut);margin:0 0 1.2rem;max-width:720px}
code,.mono{background:#0e131b;border:1px solid var(--line);border-radius:6px;padding:1px 6px;font-family:ui-monospace,monospace;font-size:13px}
pre{background:#0e131b;border:1px solid var(--line);border-radius:10px;padding:12px 14px;overflow-x:auto;
font-family:ui-monospace,monospace;font-size:12.5px;color:var(--ink);margin:.8rem 0}
.ext{background:var(--panel);border:1px solid var(--line);border-radius:14px;padding:20px 22px;margin:1rem 0}
.ext h3{margin:0 0 .3rem;font-size:1.15rem;display:flex;align-items:center;gap:10px}
.ext h3 .icon{font-size:1.4rem}
.ext .cur{color:var(--acid);font-size:12px;font-weight:600;letter-spacing:.14em;text-transform:uppercase}
.ext .desc{color:var(--mut);font-size:14px;margin:.3rem 0 .8rem}
.ext .verifybox{margin-top:.9rem;padding-top:.8rem;border-top:1px solid var(--line);font-size:11.5px;color:var(--dim)}
.ext .verifybox .lbl{color:var(--mut);font-size:12px;margin-bottom:6px}
.ext .h{display:flex;gap:8px;flex-wrap:wrap;align-items:baseline;margin-top:4px}
.ext .h b{color:var(--mut);font-weight:600;min-width:70px}
.ext .h code{font-family:ui-monospace,monospace;font-size:10.5px;color:#c9d4e3;word-break:break-all;background:transparent;border:none;padding:0}
.ext .meta{color:var(--dim);font-size:12.5px;margin-top:.4rem}
site-theseus-x/extensions: Install + Download buttons on the bundled cards Every card that has a signed update channel now carries the two buttons a reader actually needs — "Install in Theseus" (a theseus://extensions/install/<id> deep link that main.js already intercepts via will-navigate, popping the native install-consent dialog and verifying the operator signature before any bytes hit addons/) and "Download tarball" (direct .tar.gz link for sideloaders and archivists). A one-line update hint below the buttons points at the signed updates.json and notes SHA-256 verification, so the whole install-and-then-update path fits inside the card. Applies to Screenshot and PDF Editor. Notepad and Translate ship inside every Theseus build and have no separate channel yet — those carry a plain "Ships with Theseus — appears under Settings › Extensions on first launch" note in the same slot so the layout stays consistent across bundled entries. The download hrefs default to the current versioned tarball on the navigate.st gateway and get rewritten to the newest entry from the signed updates.json when the fetch succeeds (new data-live="download" setter on the manifest-fill script) so the button never points at a stale version.
2026-09-21 03:55:20 +02:00
.ext .act .download{display:inline-block;padding:9px 14px;border-radius:9px;text-decoration:none;
font-size:13.5px;font-weight:600;background:transparent;color:var(--ink);border:1px solid var(--line)}
.ext .act .download:hover{background:var(--panel)}
.ext .act .hint{color:var(--dim);font-size:11.5px;margin-left:auto;flex-basis:100%}
.ext .act .hint b{color:var(--mut);font-weight:500}
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
.ext .act{display:flex;align-items:center;gap:12px;flex-wrap:wrap;margin-top:.8rem}
.ext .install{display:inline-block;background:var(--acid);color:#0b0e14;font-weight:600;font-size:14px;
border:none;border-radius:9px;padding:9px 18px;cursor:pointer;text-decoration:none;font-family:inherit}
.ext .install:hover{filter:brightness(1.08)}
.ext .install[disabled]{opacity:.6;cursor:default}
.ext .install.alt{background:rgba(214,255,61,.12);color:var(--acid)}
.ext .act .st{font-size:13px;color:var(--mut)}
.ext .act .st.ok{color:var(--acid)} .ext .act .st.err{color:#f6768a}
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
.ext .act .how{flex-basis:100%;font-size:13px;color:var(--mut);background:#0e131b;border:1px solid var(--line);border-radius:8px;padding:8px 12px}
.ext .how b{color:var(--ink)}
.search{max-width:560px;margin:1.4rem auto 0;position:relative}
.search input{width:100%;background:var(--panel);border:1px solid var(--line);border-radius:12px;color:var(--ink);
font:inherit;font-size:15px;padding:11px 14px 11px 40px;outline:none}
.search input:focus{border-color:rgba(214,255,61,.5)}
.search svg{position:absolute;left:13px;top:50%;transform:translateY(-50%);width:17px;height:17px;color:var(--dim)}
.search .n{position:absolute;right:13px;top:50%;transform:translateY(-50%);font-size:12px;color:var(--dim)}
.ext.hide, .nomatch{display:none}
.nomatch.show{display:block}
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
.note{background:var(--panel);border:1px solid var(--line);border-left:3px solid var(--acid);
border-radius:10px;padding:14px 18px;color:var(--mut);font-size:14px;margin:1.4rem 0}
.note b{color:var(--ink)}
.pubkey{background:#0e131b;border:1px solid var(--line);border-radius:8px;padding:10px 12px;
font-family:ui-monospace,monospace;font-size:11px;color:#c9d4e3;word-break:break-all;margin:.6rem 0}
.flow{background:var(--panel);border:1px solid var(--line);border-radius:12px;padding:16px 20px;margin-top:1rem;color:var(--mut);font-size:14px}
.flow ol{margin:0;padding-left:20px}
.flow li{margin:.4rem 0}
.flow b{color:var(--ink)}
footer{color:var(--dim);font-size:12.5px;margin:3rem 0 2rem;text-align:center}
footer a{color:var(--mut)}
</style>
</head>
<body>
<nav class="topnav">
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
<a class="brand" href="../">
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<svg viewBox="0 0 64 64" aria-hidden="true">
<rect width="64" height="64" rx="12" fill="#0b0e14"/>
<path d="M32 6 L38 32 L26 32 Z" fill="#e04e4e"/>
<path d="M38 32 L32 58 L26 32 Z" fill="#d6ff3d"/>
<path d="M6 32 L32 27 L58 32 L32 37 Z" fill="#d6ff3d" opacity=".55"/>
<circle cx="32" cy="32" r="3" fill="#0b0e14"/>
</svg>
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
<span>Theseus<span class="g">.X</span></span>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</a>
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
<a href="../plug-ins/">Plug-ins</a>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<a class="here" href="./">Extensions</a>
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
<a href="../dev/">Developers</a>
site(ariadne.x, theseus.x): protocol-relative sibling links 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.
2026-10-04 19:18:32 +02:00
<a href="//sirius.x/" title="Register a BCNR name"><svg class="tabicon" viewBox="0 0 64 64" aria-hidden="true"><rect width="64" height="64" rx="12" fill="#0b0e14"/><path d="M32 4 L36.4 27.6 L60 32 L36.4 36.4 L32 60 L27.6 36.4 L4 32 L27.6 27.6 Z" fill="#d6ff3d"/></svg><span>Sirius<span class="g">.X</span></span></a>
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
<a class="get" href="../#download">Get Theseus</a>
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
<details class="menu">
<summary aria-label="Open menu">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><path d="M4 7h16M4 12h16M4 17h16"/></svg>
</summary>
<div class="menu-panel">
<a href="../plug-ins/">Plug-ins</a>
<a href="./">Extensions</a>
<a href="../dev/">Developers</a>
site(ariadne.x, theseus.x): protocol-relative sibling links 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.
2026-10-04 19:18:32 +02:00
<a href="//sirius.x/">Sirius.X</a>
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
</div>
</details>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</nav>
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
<aside class="sidenav" aria-label="On this page">
site-theseus-x: adaptive edge sidebar (labels → icons → bottom bar) Sidebar was a small strip in the middle of the page. Now it lives on the left edge as a proper column, sized to be reachable — 220px full mode with icon + label per link, on the operator's brand backdrop. Breakpoints: >1180px full sidebar, icon + label, "ON THIS PAGE" section header <=1180px 64px icon rail, labels drop, tooltips on hover <=720px bottom bar strip, icons only, spans page width body padding-left carries the sidebar width so the topnav and page content flow as one column beside the rail — no overlap on any width. Home has 4 icons (What it is / Features / Download / Verify), Plug-ins has 3 (Aegis / Ariadne's Thread / vs extensions), Extensions has 6 (Bundled / Community / Build & publish / Updates / Operator key / Roadmap).
2026-09-20 16:11:57 +02:00
<a href="#bundled" title="Bundled" ><span class="ic" aria-hidden="true">📦</span><span class="lb">Bundled</span></a>
<a href="#community" title="Community" ><span class="ic" aria-hidden="true">👥</span><span class="lb">Community</span></a>
<a href="#build" title="Build &amp; publish" ><span class="ic" aria-hidden="true">🔨</span><span class="lb">Build &amp; publish</span></a>
<a href="#updates" title="How updates work" ><span class="ic" aria-hidden="true">🔄</span><span class="lb">How updates work</span></a>
<a href="#operator-key" title="Operator key" ><span class="ic" aria-hidden="true">🔑</span><span class="lb">Operator key</span></a>
<a href="#roadmap" title="Roadmap" ><span class="ic" aria-hidden="true">🗺</span><span class="lb">Roadmap</span></a>
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
</aside>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<header class="hero">
<h1>Theseus <span class="g">Extensions</span></h1>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<p class="tag">Add-ons for Theseus Navigator — the ones that ship in the box and the ones anyone can
publish. Every package is signed (by the Silent Mode operator, or by the publisher's own BCDN name)
and verified on your device before install. No cert authority, no app-store gatekeeper.
site-theseus-x: text-only sidebar on wide, icons on narrow, relative links Sidebar redesign: - Wide (>1180px): labels only, no icons, no border-left outline, no background tint on active — just the label going acid green when the section is in view. Sidebar moved down (+34px top padding) so the first link doesn't crowd the topnav. - Medium (720-1180px): icon rail only. - Mobile (<720px): bottom bar with icons only. - Background dropped from rgba(.82) to rgba(.42) — the backdrop-blur already carries the separation, less panel-heavy against the hero. - "On this page" section header dropped: the sidebar is close enough to the topnav that the label reads as chrome rather than nav. - Active state is now colour only (acid on the label); the left border stripe and highlight background are gone. Nav path fix (broken link on the silentmode.st mirror): Root-absolute nav paths like /plug-ins/ resolved to silentmode.st/plug-ins/ (404) instead of silentmode.st/theseus/plug-ins/ when a reader browsed the fallback mirror. Rewrote every topnav link, cross-page prose link and favicon href to relative form (plug-ins/, ../plug-ins/, assets/favicon.svg, …). Works on both the BCNR name and the silentmode.st/theseus/ mount.
2026-09-20 17:07:17 +02:00
First-party plug-ins (Aegis, Ariadne's Thread) have their <a href="../plug-ins/">own page</a>.</p>
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
<div class="search">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m20 20-3.5-3.5"/></svg>
<input id="extSearch" type="search" placeholder="Search extensions — name, what it does, publisher" autocomplete="off" aria-label="Search extensions">
<span class="n" id="extSearchN"></span>
</div>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</header>
<div class="wrap">
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<section id="bundled">
<h2>Bundled extensions</h2>
<p class="lede">Ship with every Theseus build and update over the operator-signed channel. Versions and hashes
are read from each add-on's signed <code>updates.json</code> when this page loads.</p>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
<div class="ext" id="screenshot" data-ext="screenshot">
<h3><span class="icon">📸</span> Screenshot <span class="cur" style="margin-left:auto">current <span data-live="version">0.6.5</span></span></h3>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<div class="desc">Capture the current tab — visible viewport, entire scrollable page, or a rectangle
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
you draw. The capture opens in a full-tab editor: crop, annotate, line tool, resizable text,
redact, save.</div>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<div class="meta">Settings › Extensions · <span data-live="count"></span></div>
site-theseus-x/extensions: Install + Download buttons on the bundled cards Every card that has a signed update channel now carries the two buttons a reader actually needs — "Install in Theseus" (a theseus://extensions/install/<id> deep link that main.js already intercepts via will-navigate, popping the native install-consent dialog and verifying the operator signature before any bytes hit addons/) and "Download tarball" (direct .tar.gz link for sideloaders and archivists). A one-line update hint below the buttons points at the signed updates.json and notes SHA-256 verification, so the whole install-and-then-update path fits inside the card. Applies to Screenshot and PDF Editor. Notepad and Translate ship inside every Theseus build and have no separate channel yet — those carry a plain "Ships with Theseus — appears under Settings › Extensions on first launch" note in the same slot so the layout stays consistent across bundled entries. The download hrefs default to the current versioned tarball on the navigate.st gateway and get rewritten to the newest entry from the signed updates.json when the fetch succeeds (new data-live="download" setter on the manifest-fill script) so the button never points at a stale version.
2026-09-21 03:55:20 +02:00
<div class="act">
<a class="install" href="theseus://extensions/install/screenshot" data-install="screenshot">Install in Theseus</a>
<a class="download" data-live="download" href="https://navigate.st/bns/theseus.x/extensions/screenshot/screenshot-0.6.5.tar.gz" download>Download tarball</a>
<div class="hint">Updates: signed <a href="./screenshot/updates.json">updates.json</a> · SHA-256 verified before every install</div>
</div>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<div class="verifybox">
<div class="lbl">Signed update manifest — SHA-256 verified before install</div>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
<div class="h"><b>updates.json</b><code><a href="./screenshot/updates.json">theseus.x/extensions/screenshot/updates.json</a></code></div>
<div class="h"><b>Tarball</b><code><a data-live="url" href="./screenshot/screenshot-0.6.5.tar.gz">screenshot-0.6.5.tar.gz</a></code></div>
<div class="h"><b>sha256</b><code data-live="sha256">87ae730d329ff9f552bbf513efba19bd14bb016bb90e24f7b62868434dadda60</code></div>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</div>
</div>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
<div class="ext" id="notepad">
<h3><span class="icon">📝</span> Notepad <span class="cur" style="margin-left:auto">bundled 0.1.0</span></h3>
<div class="desc">Right-sidebar notes. Text lives on this machine only and autosaves as you type.</div>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<div class="meta">Settings › Extensions · no update channel yet — ships with each Theseus release.</div>
site-theseus-x/extensions: Install + Download buttons on the bundled cards Every card that has a signed update channel now carries the two buttons a reader actually needs — "Install in Theseus" (a theseus://extensions/install/<id> deep link that main.js already intercepts via will-navigate, popping the native install-consent dialog and verifying the operator signature before any bytes hit addons/) and "Download tarball" (direct .tar.gz link for sideloaders and archivists). A one-line update hint below the buttons points at the signed updates.json and notes SHA-256 verification, so the whole install-and-then-update path fits inside the card. Applies to Screenshot and PDF Editor. Notepad and Translate ship inside every Theseus build and have no separate channel yet — those carry a plain "Ships with Theseus — appears under Settings › Extensions on first launch" note in the same slot so the layout stays consistent across bundled entries. The download hrefs default to the current versioned tarball on the navigate.st gateway and get rewritten to the newest entry from the signed updates.json when the fetch succeeds (new data-live="download" setter on the manifest-fill script) so the button never points at a stale version.
2026-09-21 03:55:20 +02:00
<div class="act">
<span class="hint" style="margin-left:0"><b>Ships with Theseus</b> — nothing to install; appears under Settings › Extensions on first launch.</span>
</div>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
</div>
site-theseus-x/extensions: list PDF Editor 0.1.0 + Word editor 0.1.0 Two first-party extensions shipped without ever appearing on the catalog page. Added: 📄 PDF Editor — bundled, full-tab PDF reader/annotator (highlight, mark up, reorder/rotate/drop pages, fill forms, save a new copy; annotations written as real PDF content). Opens from the toolbar menu and from the "Open PDF in editor" right-click on any link. 📝 Word editor — .docx open/edit/save in a full Theseus tab. Ribbon-style formatting, tables, lists, images and links; headers, footers, footnotes, page setup and the document's own styles are preserved through a round-trip. Listed as a community extension (Settings › Extensions › Community); channel path mirrors the addon.json updateURL (extensions/community/docx-editor). Both cards carry data-ext hooks so the manifest-fill script picks up version + tarball + sha256 from a signed updates.json when the channel is published — for now the baked-in 0.1.0 is the fallback.
2026-09-21 01:39:55 +02:00
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
<div class="ext" id="translate">
<h3><span class="icon">🌐</span> Translate <span class="cur" style="margin-left:auto">bundled 0.1.0</span></h3>
<div class="desc">Select text on any page and right-click <i>Translate</i> — the sidebar panel shows the translation,
with LibreTranslate or Google as the backend (your choice in the panel). Nothing is sent until you ask.</div>
<div class="meta">Settings › Extensions · no update channel yet — ships with each Theseus release.</div>
site-theseus-x/extensions: Install + Download buttons on the bundled cards Every card that has a signed update channel now carries the two buttons a reader actually needs — "Install in Theseus" (a theseus://extensions/install/<id> deep link that main.js already intercepts via will-navigate, popping the native install-consent dialog and verifying the operator signature before any bytes hit addons/) and "Download tarball" (direct .tar.gz link for sideloaders and archivists). A one-line update hint below the buttons points at the signed updates.json and notes SHA-256 verification, so the whole install-and-then-update path fits inside the card. Applies to Screenshot and PDF Editor. Notepad and Translate ship inside every Theseus build and have no separate channel yet — those carry a plain "Ships with Theseus — appears under Settings › Extensions on first launch" note in the same slot so the layout stays consistent across bundled entries. The download hrefs default to the current versioned tarball on the navigate.st gateway and get rewritten to the newest entry from the signed updates.json when the fetch succeeds (new data-live="download" setter on the manifest-fill script) so the button never points at a stale version.
2026-09-21 03:55:20 +02:00
<div class="act">
<span class="hint" style="margin-left:0"><b>Ships with Theseus</b> — nothing to install; appears under Settings › Extensions on first launch.</span>
</div>
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
</div>
site-theseus-x/extensions: list PDF Editor 0.1.0 + Word editor 0.1.0 Two first-party extensions shipped without ever appearing on the catalog page. Added: 📄 PDF Editor — bundled, full-tab PDF reader/annotator (highlight, mark up, reorder/rotate/drop pages, fill forms, save a new copy; annotations written as real PDF content). Opens from the toolbar menu and from the "Open PDF in editor" right-click on any link. 📝 Word editor — .docx open/edit/save in a full Theseus tab. Ribbon-style formatting, tables, lists, images and links; headers, footers, footnotes, page setup and the document's own styles are preserved through a round-trip. Listed as a community extension (Settings › Extensions › Community); channel path mirrors the addon.json updateURL (extensions/community/docx-editor). Both cards carry data-ext hooks so the manifest-fill script picks up version + tarball + sha256 from a signed updates.json when the channel is published — for now the baked-in 0.1.0 is the fallback.
2026-09-21 01:39:55 +02:00
<div class="ext" id="pdf-editor" data-ext="pdf-editor">
theseus + site: fix duplicate extension cards + real-icon rendering - Settings > Extensions: the Community list showed an entry even for extensions already listed above under Installed, so docx-editor appeared twice as soon as it landed in the gateway catalog. The render now filters out any catalog item whose id is installed — the Installed list handles updates via the poll + "Check for updates" button, so the Community list only needs to surface things you don't have. Empty-state copy branches on whether the catalog is empty vs "everything is installed". - theseus.x/extensions catalog renderer accepts data:image/... icons in addition to emoji, so an extension whose manifest.icon is an SVG data URI (pdf-editor, docx-editor) renders as an <img> instead of the raw URI text. - Static PDF Editor entry on that page now uses the same inline SVG badge the browser dock renders.
2026-09-21 02:43:10 +02:00
<h3><span class="icon" aria-hidden="true"><svg width="20" height="20" viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg" style="vertical-align:middle"><path d="M6 2h8l6 6v12a2 2 0 0 1-2 2H6a2 2 0 0 1-2-2V4a2 2 0 0 1 2-2z" fill="#dc2626"/><path d="M14 2v6h6z" fill="#991b1b"/><text x="12" y="17" text-anchor="middle" font-family="system-ui,-apple-system,sans-serif" font-size="5.5" font-weight="800" fill="#fff">PDF</text></svg></span> PDF Editor <span class="cur" style="margin-left:auto">current <span data-live="version">0.1.0</span></span></h3>
site-theseus-x/extensions: list PDF Editor 0.1.0 + Word editor 0.1.0 Two first-party extensions shipped without ever appearing on the catalog page. Added: 📄 PDF Editor — bundled, full-tab PDF reader/annotator (highlight, mark up, reorder/rotate/drop pages, fill forms, save a new copy; annotations written as real PDF content). Opens from the toolbar menu and from the "Open PDF in editor" right-click on any link. 📝 Word editor — .docx open/edit/save in a full Theseus tab. Ribbon-style formatting, tables, lists, images and links; headers, footers, footnotes, page setup and the document's own styles are preserved through a round-trip. Listed as a community extension (Settings › Extensions › Community); channel path mirrors the addon.json updateURL (extensions/community/docx-editor). Both cards carry data-ext hooks so the manifest-fill script picks up version + tarball + sha256 from a signed updates.json when the channel is published — for now the baked-in 0.1.0 is the fallback.
2026-09-21 01:39:55 +02:00
<div class="desc">Open a PDF in a full tab — read, highlight, mark up, reorder or rotate or drop pages,
fill form fields, save a new copy. Annotations are written as real PDF content, the original
is never touched. Opens from the toolbar's PDF Editor menu or the right-click <i>Open PDF in editor</i>
on any link.</div>
<div class="meta">Settings › Extensions · <span data-live="count">signed update channel</span></div>
site-theseus-x/extensions: Install + Download buttons on the bundled cards Every card that has a signed update channel now carries the two buttons a reader actually needs — "Install in Theseus" (a theseus://extensions/install/<id> deep link that main.js already intercepts via will-navigate, popping the native install-consent dialog and verifying the operator signature before any bytes hit addons/) and "Download tarball" (direct .tar.gz link for sideloaders and archivists). A one-line update hint below the buttons points at the signed updates.json and notes SHA-256 verification, so the whole install-and-then-update path fits inside the card. Applies to Screenshot and PDF Editor. Notepad and Translate ship inside every Theseus build and have no separate channel yet — those carry a plain "Ships with Theseus — appears under Settings › Extensions on first launch" note in the same slot so the layout stays consistent across bundled entries. The download hrefs default to the current versioned tarball on the navigate.st gateway and get rewritten to the newest entry from the signed updates.json when the fetch succeeds (new data-live="download" setter on the manifest-fill script) so the button never points at a stale version.
2026-09-21 03:55:20 +02:00
<div class="act">
<a class="install" href="theseus://extensions/install/pdf-editor" data-install="pdf-editor">Install in Theseus</a>
<a class="download" data-live="download" href="https://navigate.st/bns/theseus.x/extensions/pdf-editor/pdf-editor-0.1.0.tar.gz" download>Download tarball</a>
<div class="hint">Updates: signed <a href="./pdf-editor/updates.json">updates.json</a> · SHA-256 verified before every install</div>
</div>
site-theseus-x/extensions: list PDF Editor 0.1.0 + Word editor 0.1.0 Two first-party extensions shipped without ever appearing on the catalog page. Added: 📄 PDF Editor — bundled, full-tab PDF reader/annotator (highlight, mark up, reorder/rotate/drop pages, fill forms, save a new copy; annotations written as real PDF content). Opens from the toolbar menu and from the "Open PDF in editor" right-click on any link. 📝 Word editor — .docx open/edit/save in a full Theseus tab. Ribbon-style formatting, tables, lists, images and links; headers, footers, footnotes, page setup and the document's own styles are preserved through a round-trip. Listed as a community extension (Settings › Extensions › Community); channel path mirrors the addon.json updateURL (extensions/community/docx-editor). Both cards carry data-ext hooks so the manifest-fill script picks up version + tarball + sha256 from a signed updates.json when the channel is published — for now the baked-in 0.1.0 is the fallback.
2026-09-21 01:39:55 +02:00
<div class="verifybox">
<div class="lbl">Signed update manifest — SHA-256 verified before install</div>
<div class="h"><b>updates.json</b><code><a href="./pdf-editor/updates.json">theseus.x/extensions/pdf-editor/updates.json</a></code></div>
<div class="h"><b>Tarball</b><code><a data-live="url" href="./pdf-editor/pdf-editor-0.1.0.tar.gz">pdf-editor-0.1.0.tar.gz</a></code></div>
<div class="h"><b>sha256</b><code data-live="sha256">—</code></div>
</div>
</div>
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
<div class="nomatch note" id="nomatchBundled">No bundled extension matches that search.</div>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
</section>
<section id="community">
<h2>Community extensions</h2>
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
<p class="lede">Published by BCDN name holders, signed with the wallet that holds the name. Open this page in Theseus
and click <b>Install in Theseus</b> — or use <b>Settings › Extensions › Community</b>. Either way Theseus fetches the
package itself and re-checks every signature against the name's current owner in its own chain index — the relay
cannot substitute code under a trusted name.</p>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<div id="communityList"><div class="ext" style="color:var(--dim)">Loading the catalog…</div></div>
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
<div class="nomatch note" id="nomatchCommunity">No community extension matches that search.</div>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<div class="note"><b>Trust, stated plainly.</b> A community extension runs with the same access as any add-on —
treat one like an unsigned executable from that publisher. The signature proves <i>who</i> published it,
not that it is safe.</div>
</section>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<section id="build">
<h2>Build and publish your own</h2>
<p class="lede">An extension is a folder with an <code>addon.json</code> and a main script. Package it, sign it with
the wallet that holds one of your BCDN names, and it is listed above within a minute. Nothing to apply for.</p>
<div class="flow">
<ol>
<li><b>Write it.</b> The manifest and a CommonJS entry that exports <code>activate(api)</code>:
<pre>my-ext/
addon.json {"id":"my-ext","name":"My Extension","version":"1.0.0",
"description":"…","author":"you.bch","icon":"✨",
"main":"index.js","capabilities":["sidebar-panel"]}
index.js module.exports = { activate(api) {
api.registerSidebarPanel({ id:"main", title:"My Extension", icon:"✨", page:"panel.html" });
} };
panel.html plain HTML, runs in the sidebar; window.silentmode.storage for local state</pre>
The bundled <a href="https://code.silentmode.st/silentmode/theseus/src/branch/master/TheseusNavigator/bundled-addons/notepad">Notepad</a>
is the smallest complete example; <a href="https://code.silentmode.st/silentmode/theseus/src/branch/master/TheseusNavigator/addons-host.js">addons-host.js</a>
is the full API. <code>id</code> is <code>[a-z0-9._-]</code>, 2–64 chars, and belongs to the first name that publishes it.</li>
<li><b>Test it locally.</b> Settings › Extensions › <i>Open extensions folder</i>, drop the folder in, <i>Reload</i>.</li>
<li><b>Package it.</b> <code>tar -czf my-ext-1.0.0.tar.gz -C my-ext .</code> (max 8 MB; <code>addon.json</code> at the root or in a single top folder).</li>
<li><b>Publish it.</b> Open <a class="btn" href="./publish/" style="display:inline-block;padding:.35rem .8rem;border-radius:8px;background:var(--acid);color:#0b0e14;font-weight:650;text-decoration:none">Publish an extension →</a>
sign in with the recovery phrase of the wallet that holds your name, pick the package, and sign. The gateway
verifies the signature against the name's on-chain owner, stores the package on Sia, and updates the catalog.
New versions: same page, higher version number, same name.</li>
</ol>
</div>
<p class="lede" style="margin-top:1rem">Prefer the command line? The upload is one signed <code>PUT</code>:
<code>PUT https://silentmode.st/api/ext/&lt;your-name&gt;/&lt;id&gt;/&lt;version&gt;</code> with the tarball as body and headers
<code>x-bns-ts</code>, <code>x-bns-sig</code> (over <code>sha256("BNS-EXT1\n&lt;name&gt;\n&lt;id&gt;\n&lt;version&gt;\n&lt;sha256&gt;\n&lt;ts&gt;")</code>)
and <code>x-bns-entry-sig</code> (over <code>sha256("silentmode.extension-v1|&lt;id&gt;|&lt;version&gt;|&lt;sha256&gt;|&lt;name&gt;")</code>),
both 65-byte BCH message signatures by the name's owner key.</p>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</section>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
<script>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
// Bundled cards: fill from each add-on's signed manifest (relative URLs work on every origin the page is served from).
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
(async () => {
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
const cmp = (a, b) => { const x = String(a).split(".").map(Number), y = String(b).split(".").map(Number); for (let i = 0; i < Math.max(x.length, y.length); i++) { const d = (x[i] || 0) - (y[i] || 0); if (d) return d; } return 0; };
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
for (const card of document.querySelectorAll(".ext[data-ext]")) {
const id = card.dataset.ext;
try {
const r = await fetch("./" + id + "/updates.json", { cache: "no-store" });
if (!r.ok) continue;
const m = await r.json();
const list = (m.addons || []).slice().sort((x, y) => cmp(y.version, x.version));
const top = list[0]; if (!top) continue;
const set = (k, f) => card.querySelectorAll('[data-live="' + k + '"]').forEach(f);
set("version", (el) => { el.textContent = top.version; });
set("sha256", (el) => { el.textContent = top.sha256 || "—"; });
set("url", (el) => { el.href = top.url; el.textContent = String(top.url).split("/").pop(); });
site-theseus-x/extensions: Install + Download buttons on the bundled cards Every card that has a signed update channel now carries the two buttons a reader actually needs — "Install in Theseus" (a theseus://extensions/install/<id> deep link that main.js already intercepts via will-navigate, popping the native install-consent dialog and verifying the operator signature before any bytes hit addons/) and "Download tarball" (direct .tar.gz link for sideloaders and archivists). A one-line update hint below the buttons points at the signed updates.json and notes SHA-256 verification, so the whole install-and-then-update path fits inside the card. Applies to Screenshot and PDF Editor. Notepad and Translate ship inside every Theseus build and have no separate channel yet — those carry a plain "Ships with Theseus — appears under Settings › Extensions on first launch" note in the same slot so the layout stays consistent across bundled entries. The download hrefs default to the current versioned tarball on the navigate.st gateway and get rewritten to the newest entry from the signed updates.json when the fetch succeeds (new data-live="download" setter on the manifest-fill script) so the button never points at a stale version.
2026-09-21 03:55:20 +02:00
set("download", (el) => { if (top.url) el.href = top.url; });
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
set("count", (el) => { el.textContent = list.length + " signed version" + (list.length === 1 ? "" : "s") + " on the channel"; });
} catch {}
}
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
// Community catalog
const box = document.getElementById("communityList");
const esc = (s) => String(s || "").replace(/[&<>"']/g, (c) => ({ "&":"&amp;","<":"&lt;",">":"&gt;",'"':"&quot;","'":"&#39;" })[c]);
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
// Inside Theseus every page has window.bcnr; builds since 0.3.50 add
// installExtension(id). The page only passes the catalog id — Theseus
// fetches the package, confirms in a native dialog and verifies the signature.
const inTheseus = !!window.bcnr;
const canInstall = inTheseus && typeof window.bcnr.installExtension === "function";
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
const mode = canInstall ? "bridge" : inTheseus ? "old" : "none";
const installUi = (id) => mode === "none"
? `<a class="install" href="../#download">Get Theseus to install</a><span class="st">one click from this page inside Theseus</span>`
: `<button class="install" type="button" data-install="${esc(id)}" data-mode="${mode}">Install in Theseus</button><span class="st" data-st="${esc(id)}"></span>`;
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
try {
const r = await fetch("./community/catalog.json", { cache: "no-store" });
const cat = r.ok ? await r.json() : { extensions: [] };
const list = Array.isArray(cat.extensions) ? cat.extensions : [];
if (!list.length) { box.innerHTML = '<div class="ext" style="color:var(--dim)">Nothing published yet — yours could be the first. See <a href="#build">Build and publish your own</a>.</div>'; return; }
theseus + site: fix duplicate extension cards + real-icon rendering - Settings > Extensions: the Community list showed an entry even for extensions already listed above under Installed, so docx-editor appeared twice as soon as it landed in the gateway catalog. The render now filters out any catalog item whose id is installed — the Installed list handles updates via the poll + "Check for updates" button, so the Community list only needs to surface things you don't have. Empty-state copy branches on whether the catalog is empty vs "everything is installed". - theseus.x/extensions catalog renderer accepts data:image/... icons in addition to emoji, so an extension whose manifest.icon is an SVG data URI (pdf-editor, docx-editor) renders as an <img> instead of the raw URI text. - Static PDF Editor entry on that page now uses the same inline SVG badge the browser dock renders.
2026-09-21 02:43:10 +02:00
const iconHtml = (icon) => {
const s = String(icon || "🧩");
if (/^data:image\//i.test(s)) return `<img src="${esc(s)}" alt="" style="width:20px;height:20px;vertical-align:middle">`;
return esc(s);
};
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
box.innerHTML = list.map((e) => `
<div class="ext" id="ext-${esc(e.id)}">
theseus + site: fix duplicate extension cards + real-icon rendering - Settings > Extensions: the Community list showed an entry even for extensions already listed above under Installed, so docx-editor appeared twice as soon as it landed in the gateway catalog. The render now filters out any catalog item whose id is installed — the Installed list handles updates via the poll + "Check for updates" button, so the Community list only needs to surface things you don't have. Empty-state copy branches on whether the catalog is empty vs "everything is installed". - theseus.x/extensions catalog renderer accepts data:image/... icons in addition to emoji, so an extension whose manifest.icon is an SVG data URI (pdf-editor, docx-editor) renders as an <img> instead of the raw URI text. - Static PDF Editor entry on that page now uses the same inline SVG badge the browser dock renders.
2026-09-21 02:43:10 +02:00
<h3><span class="icon">${iconHtml(e.icon)}</span> ${esc(e.name)} <span class="cur" style="margin-left:auto">v${esc(e.latest)}</span></h3>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<div class="desc">${esc(e.description)}</div>
<div class="meta">Published by <b>${esc(e.publisher)}</b> · ${esc(String(e.versions || 1))} version${e.versions === 1 ? "" : "s"} · updated ${esc(String(e.updatedAt || "").slice(0, 10))}${e.capabilities && e.capabilities.length ? " · " + esc(e.capabilities.join(", ")) : ""}</div>
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
<div class="act">${installUi(e.id)}</div>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
<div class="verifybox">
<div class="lbl">Publisher-signed channel — verified by Theseus against ${esc(e.publisher)}'s current owner</div>
<div class="h"><b>updates.json</b><code><a href="${esc(e.updatesUrl)}">${esc(String(e.updatesUrl).replace(/^https?:\/\/[^/]+\/bns\//, ""))}</a></code></div>
<div class="h"><b>Tarball</b><code><a href="${esc(e.tarballUrl)}">${esc(String(e.tarballUrl).split("/").pop())}</a></code></div>
<div class="h"><b>sha256</b><code>${esc(e.sha256)}</code></div>
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
<div class="h"><b>Link</b><code>theseus://extensions/install/${esc(e.id)}</code></div>
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
</div>
</div>`).join("");
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
box.querySelectorAll("button[data-install]").forEach((btn) => btn.addEventListener("click", async () => {
const id = btn.dataset.install, st = box.querySelector(`[data-st="${CSS.escape(id)}"]`);
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
if (btn.dataset.mode === "old") {
// This Theseus predates the page bridge: point at the path it does have.
const name = [...btn.closest(".ext").querySelector("h3").childNodes].find((x) => x.nodeType === 3 && x.textContent.trim())?.textContent.trim() || id;
let how = btn.parentElement.querySelector(".how");
if (!how) { how = document.createElement("div"); how.className = "how"; btn.parentElement.appendChild(how); }
how.innerHTML = `Your Theseus is older than this button. Open <b>Settings › Extensions</b>, scroll to <b>Community</b> and press
<b>Install</b> next to <b>${esc(name)}</b> — same signed package, same checks. Newer builds install from here in one click:
<a href="../#download">update Theseus</a>.`;
return;
}
feat(theseus): one-click "Install in Theseus" from theseus.x/extensions The extensions page could only hand out tarballs; installing meant going to Settings › Extensions › Community and finding the entry again. Pages now get window.bcnr.installExtension(id) and Theseus intercepts theseus://extensions/install/<id> links (page clicks, target=_blank and the address bar). The page only names a catalog id: Theseus fetches the catalog and package itself, asks in a native dialog the page cannot draw over, verifies the publisher signature against the name's current owner and activates the add-on — the same path a Settings install takes. One prompt at a time; an already-installed version says so instead of offering a no-op update. The site shows the button inside Theseus (feature-detected on the bridge), a "update Theseus" hint on older builds and a download hint in other browsers.
2026-09-21 02:40:05 +02:00
btn.disabled = true; st.className = "st"; st.textContent = "Confirm in the Theseus dialog…";
let r; try { r = await window.bcnr.installExtension(id); } catch (err) { r = { ok: false, error: err?.message || String(err) }; }
if (r && r.ok) { st.className = "st ok"; st.textContent = `Installed v${r.version} — signed by ${r.publisher}`; btn.textContent = "Installed"; }
else { btn.disabled = false; st.className = r?.error === "cancelled" ? "st" : "st err"; st.textContent = r?.error === "cancelled" ? "" : (r?.error || "install failed"); }
}));
feat: community extensions — publish with a BCDN name, install from Settings, theseus.x catalog Anyone who owns a BCDN name can now publish a Theseus extension, and every Theseus can install it with the publisher's signature verified locally. Gateway (Argus/src/gateway/public-gateway.mjs): PUT /api/ext/<name>/<id>/<version> takes the gzipped tar, checks two BCH message signatures against the name's current NFT owner (one authorises the upload, one is stored in the channel), inspects the package (addon.json at the root, id/version/main match, 8 MB cap), enforces first-publisher ownership of an id and monotonic versions, and writes the tarball, the extension's updates.json and community/catalog.json to Sia. GET /api/ext/catalog reads the catalog back with CORS. Theseus: lib/publisher-sig.mjs recovers the signer of a channel entry; main.js compares it with the publisher name's owner from Theseus's own chain index before installing or updating, so neither the relay nor a tampered catalog can pass off code under a trusted name. addon-updater.js gains installCommunity() and accepts publisher-signed entries in the regular update check (operator Ed25519 entries unchanged). Settings › Extensions shows the community catalog with Install / Update; Settings › Plug-ins links to theseus.x/plug-ins. theseus.x: /plug-ins/ is a separate page for the first-party plug-ins (Aegis, Ariadne's Thread) with live versions and hashes; /extensions/ lists the bundled extensions, the community catalog, and how to build and publish; /extensions/publish/ signs and uploads a package in the browser with the wallet that holds the publisher's name (session helper + wallet bundle copied alongside).
2026-09-20 15:26:30 +02:00
} catch (e) { box.innerHTML = '<div class="ext" style="color:var(--dim)">Catalog unavailable right now.</div>'; }
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
})();
fix(sirius-press): pin line endings, found by cloning the published repo Cloning the forge repo on Windows and running the suite there turned up two things a checkout inside the monorepo could never show, because this working copy has core.autocrlf=false. Git on Windows defaults to autocrlf=true, so a fresh clone gets CRLF. For most files that is cosmetic. For shell scripts it is not: install.sh copied from such a clone onto a server fails with `bash: \r: command not found`, which tells the person almost nothing about what is wrong. And a CRLF-rewritten .patch file is no longer the bytes `patch` was given. .gitattributes now pins eol=lf for the scripts, the container inputs and the source, and marks *.patch as binary so nothing rewrites it at all. tools/refresh-patches.sh --check also compares with --strip-trailing-cr, so a clone made before this landed reports honestly instead of claiming the patch record has drifted when it has not. A check that cries wolf is a check somebody switches off.
2026-09-21 03:31:16 +02:00
// Search: filters the bundled and community cards by name, description, publisher, capabilities.
(() => {
const q = document.getElementById("extSearch"), n = document.getElementById("extSearchN");
const apply = () => {
const s = q.value.trim().toLowerCase();
let shown = 0;
for (const sec of ["bundled", "community"]) {
const cards = [...document.querySelectorAll(`#${sec} .ext`)].filter((c) => c.querySelector("h3"));
let hit = 0;
for (const c of cards) { const ok = !s || c.textContent.toLowerCase().includes(s); c.classList.toggle("hide", !ok); if (ok) hit++; }
document.getElementById(sec === "bundled" ? "nomatchBundled" : "nomatchCommunity").classList.toggle("show", !!s && cards.length > 0 && hit === 0);
shown += hit;
}
n.textContent = s ? `${shown} match${shown === 1 ? "" : "es"}` : "";
};
q.addEventListener("input", apply);
new MutationObserver(() => { if (q.value.trim()) apply(); }).observe(document.getElementById("communityList"), { childList: true });
if (location.hash === "#search") q.focus();
})();
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
</script>
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
<section id="updates">
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<h2>How updates work</h2>
<p class="lede">Same mechanism a Firefox XPI update uses, cut down to what a name-native browser needs.</p>
<div class="flow">
<ol>
<li>Every 30 seconds after boot Theseus fetches <code>updates.json</code> for each installed add-on that declares an <code>updateURL</code> in its manifest.</li>
<li>Each entry carries an Ed25519 signature over <code>silentmode.addon-update-v1|&lt;id&gt;|&lt;version&gt;|&lt;sha256&gt;</code>. Theseus verifies against a small set of operator public keys baked into the build. Unsigned or badly-signed entries are dropped silently.</li>
<li>If a signed version beats what's installed, Theseus downloads the tarball, re-checks its sha256, and stages the new copy under <code>&lt;userData&gt;/addons-updates-staged/&lt;id&gt;-&lt;version&gt;/</code>.</li>
<li>On the next Theseus launch, <code>promoteStagedUpdates</code> moves the staged copy into <code>addons/&lt;id&gt;/</code>. Any prior copy is renamed to <code>addons-backups/&lt;id&gt;-&lt;oldver&gt;-&lt;timestamp&gt;/</code> so hand-edits survive.</li>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
<li>Settings › Extensions has a <b>Check for updates</b> button and shows what is staged; first-party plug-ins (Aegis) can also stage and restart from their own panel.</li>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</ol>
</div>
</section>
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
<section id="operator-key">
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<h2>Operator key</h2>
<p class="lede">The Ed25519 public key baked into Theseus 0.3.19+.
Rotation is by adding a new pubkey and shipping a Theseus release that carries both, then a follow-up release removing the old — during the overlap, entries can be signed by either.</p>
<div class="pubkey">732b1263a236b0030383a2376597cfa43c3624b3ca2912a46134f8f2a06e6012</div>
<p style="color:var(--dim);font-size:12.5px;margin-top:.6rem">Generated 2026-09-07. Held offline by the Silent Mode operator.</p>
</section>
site-theseus-x: split site-level tabs from in-page nav The top nav was a mix of anchor links (#what, #features, #verify) and site tabs (/plug-ins/, /extensions/). Sub-pages dropped the anchor-only items, so the header visibly reshuffled between pages — clicking a tab looked like a partial page break, not a navigation. Top nav is now the same five items on every page: brand → Theseus.X, Home / Plug-ins / Extensions / sirius.x / Get Theseus. Section anchors moved to a fixed left sidebar (position: fixed, sits outside the centered content column, hidden below 1180-1200px). IntersectionObserver highlights the current section in acid green as the reader scrolls. Sub-pages get their own left sidebar for the sections they actually contain (Plug-ins: 3; Extensions: 6), so the pattern is consistent across the site instead of home-only. Brand text bumped to capital T + capital X.
2026-09-20 15:54:01 +02:00
<section id="roadmap">
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
<h2>Roadmap</h2>
<p class="lede">The endpoint is generic — any bundled add-on can advertise an <code>updateURL</code>.
Concrete next-steps:</p>
<ul style="color:var(--mut);font-size:14px;line-height:1.7">
<li>On-BCNR pubkey publication so rotation is auditable end-to-end.</li>
<li>Multi-sig (N-of-M operator keys) so a single compromised private key can't push code.</li>
fix(theseus): address bar follows the page; tab strip stops blinking; extensions page - Address bar: the chrome view keeps document.activeElement on the URL input after the user clicks into the page (focus moved to the tab's own view), and the "don't clobber typed text" guard then froze the bar until something blurred the field. The guard now requires real focus (document.hasFocus()), and the field is blurred when the view loses focus. - Tab strip: rebuilt with innerHTML on every tabs event, which recreated every favicon <img> — a blink on the other tabs whenever one tab loaded, reloaded or changed title — and dropped drag state mid-gesture. Elements are now keyed by tab id (chips by group colour), updated in place, and moved into order; the strip is never rebuilt. - Settings › Extensions links to theseus.x/extensions. That page now has a card per bundled add-on with the current signed version, tarball and hash read from each add-on's updates.json at load (it still claimed Screenshot 0.2.4 while the channel serves 0.6.5).
2026-09-20 14:39:07 +02:00
<li>Extend the channel to <b>Notepad</b> (bundled, no channel yet).</li>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</ul>
</section>
<footer>
Silent Mode · <a href="https://code.silentmode.st/silentmode/theseus/src/branch/master/TheseusNavigator/docs/ADDON-UPDATES.md">source &amp; operator brief</a>
</footer>
</div>
sites: scroll-spy tracks scroll position, fires the last section on bottom The IntersectionObserver-based spy only fired when a section entered a narrow band 40–45% down the viewport. Short sections at the tail of a page — Operator key and Roadmap on theseus.x/extensions, whatever came last on the other pages — never made it into that band because the page runs out of scroll before their top crosses 40%, so their sidebar links stayed dim no matter how far the reader scrolled. Rewrote the spy across every page with a sidebar (theseus.x home / plug-ins / extensions and sirius.x home / tld / theseus / docs / admin / brand): it listens to window scroll, picks the last section whose top has crossed 35% of the viewport, and — when the window is scrolled to within 4px of the bottom — snaps to the final section regardless of where its top is. Every link in the rail can now activate. theseus.x/extensions also had the spy IIFE bundled with the manifest loader in one <script> block near the middle of the page, so at run time the parser hadn't yet reached the last three sections and only Bundled/Community/Build were ever registered. Moved the spy to its own <script> just before </body> so it sees every section that ships.
2026-09-20 19:20:30 +02:00
<script>
// Sidenav scroll-spy: highlight the section currently in view.
// Uses scroll-position tracking so short sections at the end of the page
// still activate their link when the reader scrolls to them.
(() => {
const links = document.querySelectorAll(".sidenav a[href^='#']");
if (!links.length) return;
const entries = [];
links.forEach((a) => { const el = document.querySelector(a.getAttribute("href")); if (el) entries.push({ el, link: a }); });
if (!entries.length) return;
const setActive = (link) => { links.forEach((l) => l.classList.remove("active")); link.classList.add("active"); };
const update = () => {
const doc = document.documentElement;
const scrollBottom = window.scrollY + window.innerHeight;
if (scrollBottom >= (doc.scrollHeight - 4)) { setActive(entries[entries.length - 1].link); return; }
const line = window.scrollY + window.innerHeight * 0.35;
let active = entries[0].link;
for (const e of entries) {
if (e.el.getBoundingClientRect().top + window.scrollY <= line) active = e.link;
else break;
}
setActive(active);
};
window.addEventListener("scroll", update, { passive: true });
window.addEventListener("resize", update);
update();
})();
</script>
feat(theseus.x): /extensions landing page for the signed OTA endpoint Adds site-theseus-x/extensions/index.html: a public-facing description of the signed add-on update endpoint (screenshot 0.2.3 currently, more add-ons as they gain an updateURL). Same visual language as the theseus.x home page — sticky topnav with the mark, hero, per-extension cards with the SHA-256 verify block, an operator-key panel, and a Firefox-XPI-style flow description. Roadmap section flags on-BCNR pubkey publication and multi-sig as the next security steps. Content is served from s3://bns/theseus/extensions/index.html; the Sia autosync mirrors it, so the theseus.x resolver reaches it at https://navigate.st/bns/theseus.x/extensions/. Landing at https://theseus.x/extensions on installs whose OS resolver knows the .x TLD (Ariadne's Thread users, or Theseus's own resolver on internal navigations). The specific screenshot 0.2.3 entry it advertises is already live at https://navigate.st/bns/theseus.x/extensions/screenshot/updates.json; this page just documents it.
2026-09-08 11:59:44 +02:00
</body>
</html>
Reference in a new issue Copy permalink