What's new in 2.1
deaddrop 2.1.0 shipped on 2026-11-15. The rest of this site describes 2.1. This page lists what’s new since 2.0.0. Coming from 1.0? Read Upgrading from 1.0 first.
At a glance
Section titled “At a glance”| 2.0 | 2.1 | |
|---|---|---|
What serve can serve |
Torrents (magnet, .torrent file or URL) |
Torrents, local files and directories, stdin (-), any http(s) download |
| Who can download | Anyone with the ticket | Anyone with the ticket, or only the ids you --allow |
| Ticket lifetime | Until used (or forever, with --multi-use) |
Optional deadline: --expire-after 24h |
| Notifiers | Discord, webhook | Discord, Slack, Mattermost, Rocket.Chat, Telegram, ntfy, email (SMTP), SMS (Twilio), webhook |
Interrupted fetch |
Download thrown away | Reconnects and resumes; rerunning the command picks up where it left off |
| See what’s in a drop | Download it | fetch --list (doesn’t use up a single-use download) |
| Client turned away | Bare “permission” error | A reason: busy, already downloaded, expired, replaced, not allowed |
Single-use data in --data-dir |
Kept after the download | Deleted after the download |
Serve more than torrents
Section titled “Serve more than torrents”SOURCE can now be local files and directories, stdin, or any http(s) URL:
deaddrop serve ./photos notes.txt # local files and directories, served where they aretar c dir | deaddrop serve - --name dir.tar # whatever is piped in, as one filedeaddrop serve https://example.com/x.iso # the server downloads it, then serves it- Local files are served in place and never moved, changed or deleted,
also with
--encrypt(the encrypted copies go in the data dir) and after a single-use download. -reads stdin into one file named by--name(defaultstdin).- http(s) URLs are downloaded and served as one file. If the response is a
.torrentfile, it’s downloaded as a torrent, so tracker links without.torrentin the URL work as before.--as-isserves it as a plain file. - Resets still only take torrents, so a reset token can’t make the server read its own files or fetch arbitrary URLs.
Only let specific clients in
Section titled “Only let specific clients in”# on the client, oncedeaddrop id# on the serverdeaddrop serve x.torrent --allow <id>Everyone else is turned away right after the handshake, so a leaked ticket is
useless to them. Also DEADDROP_ALLOW (comma-separated) and serve.allow. On
the client, --identity, DEADDROP_IDENTITY and fetch.identity pick
another identity file.
Allowing only specific clients →
Expiring tickets
Section titled “Expiring tickets”deaddrop serve x.torrent --expire-after 24hEach ticket stops working that long after it’s printed. Then the data is
deleted and the server exits, or with --wait-for-reset waits for the next
reset, whose ticket gets the full time again. Notifiers say when the ticket
expires, and the webhook JSON gets expires_at.
Expiring tickets →
Seven new notifiers
Section titled “Seven new notifiers”deaddrop serve x.torrent --notify slack=https://hooks.slack.com/services/<T…>/<B…>/<secret>deaddrop serve x.torrent --notify mattermost=https://mattermost.example.com/hooks/<key>deaddrop serve x.torrent --notify rocketchat=https://chat.example.com/hooks/<id>/<token>deaddrop serve x.torrent --notify telegram=<bot_token>@<chat_id>deaddrop serve x.torrent --notify ntfy=https://ntfy.sh/<long-random-topic>deaddrop serve x.torrent --notify 'email=smtps://user:[email protected][email protected]&[email protected]'deaddrop serve x.torrent --notify twilio=<account_sid>:<auth_token>@<from>/<to>All of them take +key / include_key. Email and SMS aren’t end-to-end
encrypted, so prefer another notifier for the key.
Notifications →
Better fetch
Section titled “Better fetch”- Resumes interrupted downloads. If the connection drops,
fetchreconnects and downloads only what’s missing, for up to--retry-forseconds (default 120) without progress. If it gives up or you stop it, the partial download stays in.deaddrop-<hash>, and running the same command again continues from there. fetch --listprints each file’s path and size, and a total, without downloading. It doesn’t use up a single-use server’s download (a 2.0 server does count it, so upgrade the server first).- Clear reasons when turned away: another client is downloading, the drop
was already downloaded, the ticket expired or was replaced by a reset, or
you’re not on the allow list. Only a busy slot is retried; the others stop
at once. No empty
.deaddrop-<hash>folder is left behind.
Changed in 2.1
Section titled “Changed in 2.1”- A single-use server deletes the data when its download is done, also
from a
--data-dirand also without--wait-for-reset. In 2.0 it only shut down, and the files (or their encrypted copies) and the blob store stayed in the data dir. A multi-use server still keeps its data until a reset replaces it or, with a--data-dir, after exit. Local files you serve are never deleted. - A reset that is still downloading when the server exits is deleted instead of left half-done in the data dir.
- A single-use server refuses a second client as soon as it connects.
Compatibility
Section titled “Compatibility”| Client ↓ / Server → | 2.0 | 2.1 |
|---|---|---|
| 2.0 | ✅ | ✅ (refusals show as “permission”) |
| 2.1 | ✅ (--list counts as the download on a single-use server) |
✅ |
Upgrading from 2.0
Section titled “Upgrading from 2.0”-
Upgrade.
brew upgrade deaddrop, or grab the 2.1.0 binaries. Servers and clients can be upgraded in any order. -
Check your
--data-dir. If you relied on a single-use server leaving the downloaded files there, switch to--multi-useor copy them out before the client fetches. -
Optional: add
--allow,--expire-after, or one of the new notifiers.