Expiring tickets
A single-use drop that nobody picks up stays on the server’s disk until
someone notices. --expire-after <DURATION> puts a deadline on each ticket:
deaddrop serve x.torrent --expire-after 24hHow it behaves
Section titled “How it behaves”- The clock starts when the ticket is printed, not while the torrent downloads.
- When it runs out, the ticket stops working: no new download or listing
starts, and
fetchsays the ticket expired instead of retrying. - A download that is already running may finish. Ctrl-C cuts it off.
- Then the data is deleted and the server exits. With
--wait-for-reset, it deletes the data and waits for the next reset instead, and every new ticket gets the full time again. - Local files given as the source are never deleted.
Durations
Section titled “Durations”Like 90s, 30m, 24h, 7d or 1h30m. A bare number is seconds, and 0
or never turns a config file’s expire_after off.
| Where | Setting |
|---|---|
| Command line | --expire-after 24h |
| Environment | DEADDROP_EXPIRE_AFTER=24h |
| Config file | expire_after = "24h" under [serve] |
Notifications
Section titled “Notifications”Notifiers are told when the ticket expires.
Discord and Slack show it in each reader’s own time (“expires in 23 hours”),
the others include it in the message, and the
webhook JSON gets expires_at (Unix seconds).