Hacking
Set up .env
yarn test
To Do
- Allow one-click retry
- Literate template YAML
-
.env
or something to make local development/deployment less annoying
- Make sure retry still works
Possible future ideas
- One-off request links
- Resume even after closing browser (store session ID in localStorage, derive filename from checksum)
- Upload an entire directory (client side ZIP)
- End-to-end encryption from browser to download
- Try S3 transfer acceleration first, fall back to whitelabel domain?
Known issues
Upload of a 1.5GB file aborts in Chrome on Linux, readerror type thing
Uses way too much memory uploading a 3GB file in Safari. I think streaming is keeping the file blob loaded in memory anyway.
- Can't download files with emoji in the name
rankdir=LR;
digraph finite_state_machine {
size="6,5"
initial -> authenticated;
initial -> authentication_failed;
authentication_failed -> authentication_failed [ label = "retry fails" ];
authentication_failed -> authenticated [ label = "retry succeeds" ];
authenticated -> initial [ label = "expires" ];
}