The desktop card and docs now link the Linux AppImage, .deb and tar.gz,
say what the AppImage needs (FUSE 2), and explain that Pithos keeps s3d in
the home folder on Linux when the system paths are not writable.
Covers giving each job its own S3 user, the exported JSON, using it from
the AWS CLI, restic, rclone, boto3 and the Node SDK, where the endpoint
is reachable from (local agents vs cloud agents), the narrower folder
keys on Drives on Silent Mode, and why there is no SSH key: s3d speaks
S3 only, with rclone serve sftp as the bridge for tools that need SFTP.
The desktop card said "installers coming"; it now links the installer
and portable exe, and says what quitting really does on Windows (s3d is
stopped, and anything it accepted is already on disk) instead of
promising a clean flush. The docs name where the hashes are, what
SmartScreen will say about an unsigned build, and how the account label
is filled in now.
The Share links card described the old week-long s3d links; public links
at navigate.st/sia are now the feature that works for anyone. The web
console no longer says "source release coming" because the code is public
on the forge, and canonical URLs follow the mirror to silentmode.st/pithos.
Share… now makes a link anyone can open, so the docs say what it exposes
(only that file, decrypted on navigate.st to stream it), how to switch it
off, and that it needs no public s3d address.
The docs said hosting on Silent Mode was not open yet. It is now: a
section explains moving s3d to s3.silentmode.st, the encryption, the
sharing a plain s3d cannot do, signing up with a BNS name, and public
folders at navigate.st/s3/<name>/<drive>/<folder>/.
People who want to set s3d up themselves, or with an AI assistant, had
only the feature tour. docs/ explains how Sia, the indexer, s3d, users,
keys and drives fit together; every Pithos screen; the web console and
desktop app; every s3d command, s3d.yml, the admin API and where files
live; AWS CLI and rclone setup; common tasks, troubleshooting and
limits; and a brief for AI assistants with the rule that recovery
phrases and secrets are never typed into a chat. The Markdown is the
source (published beside the page for assistants, with llms.txt
pointing to it); docs/build-docs.mjs renders the HTML.
