silentmode/pithos
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
pithos/theseus/addon.json

21 lines
1.2 KiB
JSON
Raw Normal View History

Pithos: a control panel for s3d, the Sia S3 gateway s3d is driven entirely by a CLI and a two-route admin API, which keeps Sia storage out of reach for anyone who does not live in a terminal. Pithos wraps it: install the pinned s3d release (checksum verified), start/stop and logs, indexer login, users and access keys, a bucket and object browser with share links and public-read policies, and the upload pipeline stats. One control server (core/) serves one UI (ui/), and three hosts run it: a web console, an Electron desktop window and a Theseus add-on, so a feature lands everywhere at once. The server binds loopback, rejects foreign Host headers, and signs views in with a one-time secret that becomes a SameSite=Strict cookie. s3d login reads the recovery phrase with term.ReadPassword, so it is driven through a pty, with a console window fallback where the pty module is not shipped.
2026-10-03 19:02:50 +02:00
{
"id": "pithos",
"name": "Pithos",
Pithos 0.3.24: one-click Share with 10-year links, share links inside Theseus, Theseus ID linking
2026-10-07 19:37:17 +02:00
"version": "0.3.24",
Pithos 0.2.0: live in the Theseus sidebar, no loopback address In Theseus the console opened as a tab at http://127.0.0.1:<port>, a raw local address in the URL bar. It is now a left-sidebar panel instead, loading the add-on's own ui/index.html: API calls, uploads and live events cross the add-on IPC bridge and the add-on forwards them to the control server with an internal session. Downloads go to Theseus's download manager through single-use 60-second links. The panel can widen to full window or open as a tab. The core gains internalSession() and downloadUrl() for that; web and desktop hosts keep talking HTTP as before. Grids now shrink to fit, so narrow hosts never scroll sideways.
2026-10-03 19:34:53 +02:00
"description": "Run s3d, the Sia S3 gateway, from the Theseus sidebar: connect it to a Sia indexer, create S3 users and access keys, browse and share buckets, and watch uploads reach Sia.",
Pithos: a control panel for s3d, the Sia S3 gateway s3d is driven entirely by a CLI and a two-route admin API, which keeps Sia storage out of reach for anyone who does not live in a terminal. Pithos wraps it: install the pinned s3d release (checksum verified), start/stop and logs, indexer login, users and access keys, a bucket and object browser with share links and public-read policies, and the upload pipeline stats. One control server (core/) serves one UI (ui/), and three hosts run it: a web console, an Electron desktop window and a Theseus add-on, so a feature lands everywhere at once. The server binds loopback, rejects foreign Host headers, and signs views in with a one-time secret that becomes a SameSite=Strict cookie. s3d login reads the recovery phrase with term.ReadPassword, so it is driven through a pty, with a console window fallback where the pty module is not shipped.
2026-10-03 19:02:50 +02:00
"author": "Silent Mode",
"icon": "data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCA2NCA2NCI+PGRlZnM+PGxpbmVhckdyYWRpZW50IGlkPSJnIiB4MT0iMCIgeTE9IjAiIHgyPSIwIiB5Mj0iMSI+PHN0b3Agb2Zmc2V0PSIwIiBzdG9wLWNvbG9yPSIjM2RkYzk3Ii8+PHN0b3Agb2Zmc2V0PSIxIiBzdG9wLWNvbG9yPSIjMWU4ZjZhIi8+PC9saW5lYXJHcmFkaWVudD48L2RlZnM+PHBhdGggZD0iTTIyIDZoMjB2NWMwIDItMiAzLTIgNSA4IDMgMTQgMTEgMTQgMjEgMCAxMi05IDIxLTIyIDIxUzEwIDQ5IDEwIDM3YzAtMTAgNi0xOCAxNC0yMSAwLTItMi0zLTItNXoiIGZpbGw9InVybCgjZykiLz48cGF0aCBkPSJNMTQgMzBoMzZNMTMgNDBoMzgiIHN0cm9rZT0iIzBiMWYxOCIgc3Ryb2tlLXdpZHRoPSIzIiBzdHJva2UtbGluZWNhcD0icm91bmQiIG9wYWNpdHk9Ii41NSIvPjwvc3ZnPgo=",
"main": "index.js",
"capabilities": [
Pithos 0.3.0: PIN gate and a recovery phrase from the Theseus vault In Theseus, Pithos now opens only with the vault unlocked: it asks Theseus for the unlock (api.vault.requestUnlock), and Theseus shows its own PIN prompt, falling back to the master password after three wrong tries. Pithos never sees either. When the vault locks (Settings > Lock now) Pithos locks within a few seconds; the add-on watches from the main process because a hidden panel's timers run about once a minute. The guide's phrase step gains "Use my Theseus vault" (the default when a vault exists): the add-on derives the 12-word phrase from the vault (purpose path pithos/sia-recovery/v1, first 16 bytes as BIP-39 entropy) and hands it straight to s3d, so there is nothing to write down and the vault backup restores storage access. The path is now fixed; changing it would cut users off from their data. Needs the vault-derive capability. On a Theseus without requestUnlock it runs ungated, as before.
2026-10-03 20:42:21 +02:00
"sidebar-panel",
Pithos 0.3.10: the app at pithos.sia/<user>/<drive>/<folder> Full page opened Pithos at a loopback address such as 127.0.0.1:58678/#/buckets/music-house, which means nothing to anyone reading it and changes every launch. In Theseus the app now lives at pithos.sia/<S3 user>/<drive>/<folder>, with pages at pithos.sia/settings, /account and so on; the root page stays the pithos.sia website. The add-on answers those paths through Theseus's new site routes. It passes the session to the control server only for pithos.sia's own requests and the address bar, never another site's fetch, and only while the vault is unlocked, as the sidebar panel requires. The server answers its own files, pages and existing S3 users and reports anything else as not its own, so the website answers it. The sidebar and the web console keep #/ addresses; an older Theseus still gets the loopback address.
2026-10-04 03:29:28 +02:00
"vault-derive",
Pithos: open the app in a browser, also from the pithos.sia website Pithos runs on the user's computer, so the pithos.sia website could only describe it. Two ways in now: - Open in browser (Theseus, desktop) opens the current page in the default browser with a one-time sign-in link (60 s, single use), unlike the host's reusable ?t= link. - The website links to http://127.0.0.1:47621/open?path=/<user>/<drive>. Any page or local program could follow that link, so the host first asks the user in its own window (a native dialog on the desktop, Theseus's approval prompt with the vault unlocked). Only loopback Host names are accepted, one question at a time, and the website learns nothing either way. Sessions started this way are marked external, so the browser does not get host-only controls such as Back to sidebar.
2026-10-05 01:47:12 +02:00
"site-route",
Pithos: link the Theseus ID after signing in; an account console In Theseus, Pithos now links the person's Theseus ID to their hosted account by itself, once, right after signing in to Silent Mode (or on the first look at an account already signed in): one consent prompt, then Pithos is listed under Settings › Theseus ID. On a Theseus without the add-on API it does nothing, so the add-on can ship before the Theseus release that carries it. The gateway serves /console on its own origin: sign in with the Theseus ID and see the account's state, sign-up, usage and Theseus ID, with a console session that cannot reach files. Three fixed files under a CSP that allows only this origin. The bundled copy in TheseusNavigator/bundled-addons/pithos is rebuilt from Pithos/ with no version bump; the release that ships it bumps the version.
2026-10-06 20:43:14 +02:00
"approval-modal",
"theseus-id"
Pithos: a control panel for s3d, the Sia S3 gateway s3d is driven entirely by a CLI and a two-route admin API, which keeps Sia storage out of reach for anyone who does not live in a terminal. Pithos wraps it: install the pinned s3d release (checksum verified), start/stop and logs, indexer login, users and access keys, a bucket and object browser with share links and public-read policies, and the upload pipeline stats. One control server (core/) serves one UI (ui/), and three hosts run it: a web console, an Electron desktop window and a Theseus add-on, so a feature lands everywhere at once. The server binds loopback, rejects foreign Host headers, and signs views in with a one-time secret that becomes a SameSite=Strict cookie. s3d login reads the recovery phrase with term.ReadPassword, so it is driven through a pty, with a console window fallback where the pty module is not shipped.
2026-10-03 19:02:50 +02:00
],
Pithos 0.3.10: the app at pithos.sia/<user>/<drive>/<folder> Full page opened Pithos at a loopback address such as 127.0.0.1:58678/#/buckets/music-house, which means nothing to anyone reading it and changes every launch. In Theseus the app now lives at pithos.sia/<S3 user>/<drive>/<folder>, with pages at pithos.sia/settings, /account and so on; the root page stays the pithos.sia website. The add-on answers those paths through Theseus's new site routes. It passes the session to the control server only for pithos.sia's own requests and the address bar, never another site's fetch, and only while the vault is unlocked, as the sidebar panel requires. The server answers its own files, pages and existing S3 users and reports anything else as not its own, so the website answers it. The sidebar and the web console keep #/ addresses; an older Theseus still gets the loopback address.
2026-10-04 03:29:28 +02:00
"updateURL": "https://navigate.st/bns/theseus.x/extensions/pithos/updates.json",
"siteRoutes": [
"pithos.sia"
]
Pithos: a control panel for s3d, the Sia S3 gateway s3d is driven entirely by a CLI and a two-route admin API, which keeps Sia storage out of reach for anyone who does not live in a terminal. Pithos wraps it: install the pinned s3d release (checksum verified), start/stop and logs, indexer login, users and access keys, a bucket and object browser with share links and public-read policies, and the upload pipeline stats. One control server (core/) serves one UI (ui/), and three hosts run it: a web console, an Electron desktop window and a Theseus add-on, so a feature lands everywhere at once. The server binds loopback, rejects foreign Host headers, and signs views in with a one-time secret that becomes a SameSite=Strict cookie. s3d login reads the recovery phrase with term.ReadPassword, so it is driven through a pty, with a console window fallback where the pty module is not shipped.
2026-10-03 19:02:50 +02:00
}
Reference in a new issue Copy permalink