<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>deaddrop releases</title>
    <link>https://deaddrop.rip/docs/releases/</link>
    <atom:link href="https://deaddrop.rip/releases.xml" rel="self" type="application/rss+xml" />
    <description>New releases of deaddrop and what changed in each.</description>
    <language>en</language>
    <lastBuildDate>Sun, 15 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>deaddrop 2.1.0</title>
      <link>https://deaddrop.rip/docs/releases/#v2-1-0</link>
      <guid isPermaLink="false">deaddrop-v2.1.0</guid>
      <pubDate>Sun, 15 Nov 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<h3 id="changed">Changed</h3>
<ul>
<li><strong>A single-use server deletes the data when its download is done</strong>, also
from a <code>--data-dir</code> and also without <code>--wait-for-reset</code>. Before, it only
shut down, and the files (plaintext, or the encrypted copies with
<code>--encrypt</code>) and blob store stayed in a <code>--data-dir</code>. A multi-use server
still keeps its data until a reset replaces it or, with a <code>--data-dir</code>,
after exit.</li>
<li>A reset that is still downloading when the server exits is deleted instead
of left half-done in the data dir.</li>
</ul>
<h3 id="added">Added</h3>
<ul>
<li>
<p><strong>Mattermost and Rocket.Chat notifiers.</strong> <code>--notify mattermost=&lt;URL&gt;</code> and
<code>--notify rocketchat=&lt;URL&gt;</code> (or <code>type = "mattermost"</code> / <code>"rocketchat"</code> in
<code>[[serve.notify]]</code>) post the ticket to an incoming webhook, with the fetch
command in a code block. Names can’t ping anyone: Mattermost gets escaped
Markdown with <code>@</code> mentions broken up, and Rocket.Chat shows the name as a
plain-text attachment title. <code>+key</code> / <code>include_key</code> adds the decryption key.</p>
</li>
<li>
<p><strong>Email notifier.</strong> <code>--notify 'email=smtps://user:pass@smtp.example.com?from=me@x.org&amp;to=you@y.org'</code> (or
<code>type = "email"</code> with <code>url</code>, <code>from</code> and <code>to</code> in <code>[[serve.notify]]</code>) emails
the ticket and fetch command over SMTP. <code>smtps://</code> uses TLS from the start
and <code>smtp://</code> requires STARTTLS; <code>?tls=none</code> is for local relays, and a
password is never sent without TLS except to localhost. <code>to</code> takes several
recipients. <code>+key</code> / <code>include_key</code> adds the decryption key, though email
isn’t end-to-end encrypted.</p>
</li>
<li>
<p><strong>Slack notifier.</strong> <code>--notify slack=&lt;incoming webhook URL&gt;</code> (or
<code>type = "slack"</code> in <code>[[serve.notify]]</code>) posts the ticket to a Slack
channel, with the fetch command in a code block and the expiry in each
reader’s time zone. <code>+key</code> / <code>include_key</code> adds the decryption key.</p>
</li>
<li>
<p><strong>Twilio SMS notifier.</strong> <code>--notify twilio=&lt;account_sid&gt;:&lt;auth_token&gt;@&lt;from&gt;/&lt;to&gt;</code> (or <code>type = "twilio"</code> in
<code>[[serve.notify]]</code>) texts the ticket and fetch command to a phone number.
<code>from</code> can be a Twilio number, an alphanumeric sender id or a Messaging
Service; <code>api_key</code> logs in with a Twilio API key and <code>api_url</code> picks
another API host. <code>+key</code> / <code>include_key</code> adds the decryption key, though
SMS isn’t end-to-end encrypted.</p>
</li>
<li>
<p><strong>Telegram notifier.</strong> <code>--notify telegram=&lt;bot_token&gt;@&lt;chat_id&gt;</code> (or
<code>type = "telegram"</code> with <code>bot_token</code> and <code>chat_id</code> in <code>[[serve.notify]]</code>)
sends the ticket as a message from your bot, with the fetch command in a
copyable block. Optional <code>thread_id</code> posts in a forum topic and <code>api_url</code>
uses a self-hosted Bot API server. <code>+key</code> / <code>include_key</code> adds the
decryption key as a spoiler.</p>
</li>
<li>
<p><strong>ntfy notifier.</strong> <code>--notify ntfy=https://ntfy.sh/&lt;topic&gt;</code> (or
<code>type = "ntfy"</code> in <code>[[serve.notify]]</code>) sends the ticket as a push
notification to an <a href="https://ntfy.sh">ntfy</a> topic, on ntfy.sh or a
self-hosted server. Protected topics take <code>user:pass@</code> in the URL or a
<code>token</code>, and <code>priority</code> (1-5) is optional. <code>+key</code> / <code>include_key</code> adds the
decryption key to the message.</p>
</li>
<li>
<p><strong><code>serve</code> can serve more than torrents.</strong> <code>SOURCE</code> can now also be:</p>
<ul>
<li><strong>local files and directories</strong> (one or more): served where they are,
never moved, changed or deleted, also with <code>--encrypt</code> and after a
single-use download. A directory keeps its name as the top folder;
symlinks inside it, special files and empty folders are skipped.</li>
<li><strong><code>-</code> for stdin</strong>, saved as one file named by <code>--name</code> (default
<code>stdin</code>).</li>
<li><strong>any http(s) URL</strong>, which the server downloads and serves as one file
(named by <code>--name</code>, <code>Content-Disposition</code> or the URL). A response that is
a <code>.torrent</code> file (by <code>Content-Type</code> or its contents) is still downloaded
as a torrent, so tracker links without <code>.torrent</code> in the URL work as
before.</li>
</ul>
<p><code>--as-is</code> serves a <code>.torrent</code> file or URL as a plain file. Magnet URIs,
local <code>.torrent</code> files and URLs ending in <code>.torrent</code> work as before. Resets
still only take torrents, so a reset token can’t make the server read its
own files or fetch arbitrary URLs.</p>
</li>
<li>
<p><strong><code>serve --allow &lt;ID&gt;</code> lets only specific clients download.</strong> A client
runs the new <code>deaddrop id</code> command once to create a persistent identity
and gives the printed id to the server’s operator. Everyone else is turned
away right after the handshake, so a leaked ticket is useless to them, and
<code>fetch</code> stops at once with a clear message instead of retrying. Repeatable,
<code>DEADDROP_ALLOW</code> (comma-separated) or <code>serve.allow</code>. <code>fetch</code> uses the
identity once it exists (<code>--identity</code>, <code>DEADDROP_IDENTITY</code> or
<code>fetch.identity</code> pick another file); without one it still uses a new random
id each time.</p>
</li>
<li>
<p><strong><code>serve --expire-after &lt;DURATION&gt;</code> makes tickets expire.</strong> Each ticket
stops working that long after it is printed (<code>30m</code>, <code>24h</code>, <code>7d</code>, <code>1h30m</code>)
if it hasn’t been used up. Then the data is deleted and the server exits,
or with <code>--wait-for-reset</code> waits for the next reset, whose ticket gets the
full time again. A download already running may finish. Also
<code>DEADDROP_EXPIRE_AFTER</code> and <code>serve.expire_after</code>. Notifications say when
the ticket expires: <code>expires_at</code> (Unix seconds) in webhook JSON, a
relative time in Discord.</p>
</li>
<li>
<p><strong>The server says why it turns a client away</strong>, and <code>fetch</code> explains it
instead of a bare “permission” error: another client is downloading from
this single-use server, the drop was already downloaded, the ticket
expired or was replaced by a reset, or the client isn’t on the allow
list. Only a busy slot is retried, quietly (one line, not one per
attempt); the others stop at once. A single-use server now refuses a
second client as soon as it connects. If the server disappears while a
client waits for a busy slot, <code>fetch</code> says the other download most likely
finished. The server logs every refusal, and <code>fetch</code> no longer leaves an
empty <code>.deaddrop-&lt;hash&gt;</code> folder behind, or keeps a partial download that
can never be finished.</p>
</li>
<li>
<p><strong><code>fetch --list</code> shows what’s in a drop without downloading it</strong>: each
file’s path and size on stdout, and a total. Only the names and sizes are
fetched, and the server doesn’t count that as the single-use download, so
the real <code>fetch</code> still works afterwards. With <code>--encrypt</code> data the names
are shown only with the key. A server older than 2.1 does count a listing
as its one download.</p>
</li>
<li>
<p><strong><code>fetch</code> resumes interrupted downloads.</strong> If the connection drops, it
reconnects and downloads only what is missing, for up to <code>--retry-for</code>
seconds (<code>fetch.retry_for</code>, default 120) without progress. If it gives up
or is stopped, the partial download is kept in <code>.deaddrop-&lt;hash&gt;</code>, and
running the same command again picks up where it left off. Before, a
failed download was thrown away. A single-use server already let a client
that dropped out before finishing connect again.</p>
</li>
</ul>
<p><a href="https://github.com/asheliahut/deaddrop/releases/tag/v2.1.0">Download deaddrop 2.1.0</a></p>]]></description>
    </item>
    <item>
      <title>deaddrop 2.0.0</title>
      <link>https://deaddrop.rip/docs/releases/#v2-0-0</link>
      <guid isPermaLink="false">deaddrop-v2.0.0</guid>
      <pubDate>Fri, 13 Nov 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<h3 id="breaking">Breaking</h3>
<ul>
<li><strong>age encryption is now off by default.</strong> In 1.0, every file was always
age-encrypted and <code>serve</code> always printed a decryption key. In 2.0, <code>serve</code>
sends the files as they are (iroh still encrypts the connection end to end)
unless you pass <code>--encrypt</code> or set <code>serve.encrypt = true</code>. To keep the 1.0
behaviour, add <code>encrypt = true</code> under <code>[serve]</code> in your config file.</li>
<li><strong>stdout format depends on encryption.</strong> <code>serve</code> and <code>reset</code> print one line
per ticket on stdout: <code>&lt;ticket&gt;</code> without encryption, <code>&lt;ticket&gt; &lt;key&gt;</code> with
<code>--encrypt</code> (and <code>&lt;ticket&gt;</code> again with <code>--hide-key</code>). Scripts that do
<code>read -r TICKET KEY</code> still work, but <code>KEY</code> is empty when there is no key to
show.</li>
<li><strong>A 2.0 client can’t download from a 1.0 single-use server.</strong> Before
downloading, the client now sends a small size-probe request so it can show
a total and an ETA. A 1.0 single-use server counts that probe as the
download and then refuses the real one. Upgrade servers and clients
together. A 1.0 multi-use server still works.</li>
</ul>
<h3 id="added">Added</h3>
<ul>
<li><strong><code>deaddrop skill</code></strong> installs an <a href="https://agentskills.io">Agent Skill</a>
that teaches AI coding agents to use deaddrop and to set up its config file
step by step. It ships <code>SKILL.md</code> plus <code>references/config.md</code>, generated
from this version’s config template.
<ul>
<li><code>install</code>, <code>uninstall</code>, <code>status</code> and <code>show</code> subcommands.</li>
<li><code>--global</code> (your user) or <code>--project</code> (the enclosing git repository, or
<code>--dir</code>).</li>
<li><code>--harness claude,codex,copilot,agents</code> or <code>--all</code>, writing to
<code>.claude/skills</code>, <code>.agents/skills</code>, <code>.copilot/skills</code> (global) and
<code>.github/skills</code> (project).</li>
<li>Asks interactively on a terminal when the scope or agents aren’t given,
pre-selecting the agents it finds.</li>
<li>Never replaces or removes a <code>deaddrop</code> skill it didn’t write unless you
pass <code>--force</code>, and keeps other files in the skill folder on uninstall.</li>
<li>The skill is also committed at <code>skills/deaddrop/</code>, so tools that install
skills straight from a GitHub repository can use it too.</li>
</ul>
</li>
<li><strong><code>--encrypt</code> / <code>serve.encrypt</code>:</strong> opt-in age encryption at rest. Files are
encrypted with a new X25519 key per torrent, the plaintext is deleted, and
file names are hidden in an encrypted manifest, as in 1.0.</li>
<li><strong><code>--hide-key</code> / <code>serve.hide_key</code>:</strong> with <code>--encrypt</code>, the decryption key is
never printed on stderr or stdout, and never sent back to <code>deaddrop reset</code>.
Only notifiers with <code>include_key</code> (<code>+key</code>) receive it. The server refuses to
start if no notifier would receive the key, and prints an error if every
one of them failed to send. Without <code>--encrypt</code>, the setting has no effect.</li>
<li><strong><code>[relay]</code> config section</strong> for iroh’s relay servers, used by <code>serve</code>,
<code>fetch</code> and <code>reset</code>:
<ul>
<li><code>mode = "default"</code>: n0’s public relays (same as 1.0).</li>
<li><code>mode = "custom"</code> with <code>urls = [...]</code>: only your relays, for example your
own <code>iroh-relay</code>. Setting <code>urls</code> alone implies <code>custom</code>.</li>
<li><code>mode = "disabled"</code>: no relays, so a transfer only works if the two sides
can reach each other directly or by hole punching.</li>
<li>Invalid combinations are errors at startup, and <code>deaddrop config check</code>
shows the setting.</li>
</ul>
</li>
<li><strong>Connection path reporting:</strong> every connection prints whether it uses a
relay or a direct path, and prints again when it switches, for example:
<code>connection to e86045b272 switched to a direct path (203.0.113.7:50687)</code>.
This works on the server, the client and <code>reset</code>.</li>
<li><strong>Progress bars (indicatif)</strong> on stderr when it’s a terminal:
<ul>
<li><code>serve</code>: a bar for the torrent download (spinner while metadata resolves,
then bytes, speed, ETA and peer count).</li>
<li><code>serve</code>: one bar per client transfer, named by the client’s short id.
With <code>--multi-use</code>, several run at once.</li>
<li><code>fetch</code>: a bar for the download, with total size and ETA.</li>
<li>Finished bars become one-line summaries, e.g.
<code>✔ sent 500.00 MiB in 6.3s (79.42 MiB/s) to b2319767b8</code>.</li>
<li>Status lines (client connected, notifications, connection paths) print
above the bars without breaking them.</li>
</ul>
</li>
<li><strong><code>fetch</code> keeps the download when the key is missing.</strong> If the data is
encrypted and no key was given, the download stays in <code>.deaddrop-&lt;hash&gt;</code>
in the output folder. Running the same command again with the key finishes
without contacting the server, even after a single-use server has shut
down.</li>
<li><code>fetch</code> works out by itself whether the data is encrypted. If you pass a
key for data that isn’t encrypted, it prints a note and ignores the key.</li>
</ul>
<h3 id="changed">Changed</h3>
<ul>
<li><strong>Plain progress output when stderr isn’t a terminal</strong> (logs, systemd,
pipes): no bars, just a progress line every few seconds and a summary at
the end. The torrent progress line keeps its 1.0 format.</li>
<li><strong><code>--no-progress</code> / <code>DEADDROP_NO_PROGRESS</code> / <code>progress = false</code></strong> force
plain progress lines even on a terminal, for recorded sessions (<code>script</code>,
tmux logging, CI pseudo-terminals). <code>TERM=dumb</code> does the same.</li>
<li><strong>Log lines have no color codes unless stderr is a terminal.</strong> 1.0 colored
<code>tracing</code> log lines even when written to a file or pipe. Colors now follow
<code>NO_COLOR</code>, <code>CLICOLOR=0</code>, <code>CLICOLOR_FORCE</code> and <code>TERM=dumb</code>, like the
progress bars.</li>
<li><strong>Single-use gate:</strong> size-probe requests are answered but never count as
the one download.</li>
<li>Notifiers send the decryption key only when the data is encrypted, and only
to notifiers with <code>include_key</code>. Without <code>--encrypt</code>, every notifier gets
just the ticket.</li>
<li><strong>Docs:</strong>
<ul>
<li>The package description, <code>--help</code> text, README, <code>SECURITY.md</code> and
<code>config.example.toml</code> describe age encryption as an optional extra layer.</li>
<li>They document <code>--hide-key</code>, <code>[relay]</code>, connection paths, progress output,
<code>--no-progress</code> and <code>deaddrop skill</code>, and <code>--help</code> has examples for them.</li>
<li><code>SECURITY.md</code> now covers size probes, <code>deaddrop skill</code>, what relays can
see, and hardening tips for <code>--hide-key</code> and running your own relay.</li>
</ul>
</li>
<li><strong>Releases:</strong> GitHub release notes now come from this changelog (the tag’s
section must exist, or the release fails early). Release archives include
<code>CHANGELOG.md</code>. The Homebrew formula’s description no longer says the data
is always age-encrypted.</li>
</ul>
<h3 id="dependencies">Dependencies</h3>
<ul>
<li>Added <code>indicatif</code> 0.18.6.</li>
</ul>
<p><a href="https://github.com/asheliahut/deaddrop/releases/tag/v2.0.0">Download deaddrop 2.0.0</a></p>]]></description>
    </item>
    <item>
      <title>deaddrop 1.0.0</title>
      <link>https://deaddrop.rip/docs/releases/#v1-0-0</link>
      <guid isPermaLink="false">deaddrop-v1.0.0</guid>
      <pubDate>Tue, 10 Nov 2026 00:00:00 GMT</pubDate>
      <description><![CDATA[<p>First release: leech a torrent on a server without seeding it, age-encrypt
it, and hand it to one client peer to peer over iroh. Includes single-use and
multi-use serving, resets with a reset token, <code>--wait-for-reset</code>, Discord and
webhook notifiers, a TOML config file and shell completions.</p>
<p><a href="https://github.com/asheliahut/deaddrop/releases/tag/v1.0.0">Download deaddrop 1.0.0</a></p>]]></description>
    </item>
  </channel>
</rss>
