# Theirway for files

File delivery for builds, installers and documents, at https://theirway.app/files

Add new files. Keep the same client link. Upload each new build or
document to the same delivery: your client opens the link they already
have, sees what is new and downloads the files they need. Their page lists
the files by the day they arrived, newest first. When a version ships, make
a snapshot, a frozen copy of the files you choose with a link of its own.
Your client needs no account. Invite only: write to hello@theirway.app and
say what you send, and to whom.

## What it does

- **One link.** Upload the files once, with their folders as you made them.
  Add release notes, plain text, that show at the top of your client's page.
  A delivery you send once and leave is the plain case.
- **Kept up to date.** Turn on keeping a delivery up to date and add each
  new build to it, under the same link. Your client's page lists the files
  by the day they arrived, newest first, and marks what is new since they
  last looked. You add the builds; nothing arrives by itself.
- **Retract and prune.** Retract a file with a reason: your client still
  sees it listed, struck through, with your reason. Their page can't get a
  new link to it after that, though one it asked for before works for up to
  15 minutes: a download can still start in that time, one under way may
  finish, and a copy they already downloaded stays theirs.
  You can reinstate it. Prune removes a file for good. On a delivery shown
  as Files, your client's page keeps a line for it with its name, size and
  checksum, if it has one. Your trail records each move. A retraction stays
  in its delivery unless you choose to retract the file from its snapshots
  too; a prune never reaches a snapshot.
- **Snapshots.** When a version ships, choose its files and make a snapshot,
  a frozen copy with its own links and one snapshot tag, such as v2.4.1,
  that never moves. No file can be added to it or changed, though you can
  still retract one. It takes no more of your storage, and the delivery you
  keep up to date carries on as it is. Each file in it needs a checksum.
  You give your client the snapshot's link; their page for the delivery you
  keep up to date does not list its snapshots.
- **A file list to check.** A snapshot's page has a Download SHA256SUMS
  button, the list of its files' checksums, and the Checksum of the file
  list: the SHA-256 of that SHA256SUMS file, not of any one file. The link
  email carries neither, so send the checksum from your own mail. Your
  client runs `sha256sum -c SHA256SUMS` on what they downloaded, then
  `sha256sum SHA256SUMS` and compares it with yours.
- **A checksum beside each file that has one.** Each file shows its size,
  and its SHA-256 as reported when it was uploaded (for a file Theirway took
  out of a zip, the one it worked out), with a button to copy it. A file
  with none says "No checksum recorded.": one uploaded without a checksum,
  and some files added through a request link.
- **Sent as a link.** Files go from your browser straight to storage, in
  parts, and an interrupted upload picks up where it stopped. Your email
  carries a link, not the files.
- **Your client chooses.** They download one file, several, or a selection
  as a zip, several for a big one, or one by one in a browser that can't
  save a zip that large.
- **You see when it's opened.** Your delivery's activity list shows when your
  client opens the link and when they start the download.
- **Or to their own server.** Turn it on for a delivery, and your client can
  have the files sent to their SFTP server or S3 bucket. Your activity list
  shows when the files were sent, which is not when they arrived.
- **Ask for files.** Send a link to your suppliers or clients and they add
  files from their own computers, with no account. When you ask for any file,
  which is where the app starts on a Files delivery, what they add waits for
  you: nobody you sent the delivery to sees a file until you release it, and
  you can download it first to look. Zip files are kept as they were sent.
- **Stored in the EU.** In France, with OVHcloud.

## The video

A 30-second video with music and no speech, on the page at
https://theirway.app/files: one link kept up to date, with a new build
added at the same address, a broken one retracted with a reason, and a
frozen copy of a version on a link of its own. The video is
https://theirway.app/media/theirway-film-files.mp4 and its words, screen by
screen, are https://theirway.app/media/theirway-film-files-transcript.txt

## What it is not

- A checksum is a check, not a signature. It is the one reported when the
  file was uploaded (the app works it out in your browser; an upload through
  the API sends its own, if it sends one; for a file Theirway took out of a zip, Theirway
  works it out), so it helps your client notice a damaged download
  and says nothing about who made the file. Sign your builds, and
  give your client the checksum from your own mail: they work out the
  SHA-256 of the file they downloaded and compare it with yours.
- Not a place to publish: a link is for the people you send it to.
- Not open to everyone yet: accounts are invite only. Join the waiting list
  at https://theirway.app/files#join; confirming your email does not create
  an account. We email an invitation when there is a place.
- No machine address for the latest build, and no webhooks. People download
  by hand.
- A delivery is never frozen where it stands: freezing makes a snapshot, a
  new delivery with its own links. A snapshot is made when you make one.

## For agents

A public API does the same as the app, with a personal access token that a
signed-in person makes under Access tokens. A CI job can upload each build
into a delivery you keep up to date and make a snapshot of a version: the
calls, in order, are at https://theirway.app/agents#ci. See
https://theirway.app/agents (or https://theirway.app/agents.md) and the
OpenAPI document at https://theirway.app/api/v1/openapi.json.

## Elsewhere

- Privacy notice: https://theirway.app/privacy.html
- Report illegal or abusive content: https://theirway.app/report.html
- Machine-readable index: https://theirway.app/files/llms.txt
- Theirway's front page, for pictures, film and any other files: https://theirway.app/
