FDM v2.10.1

feat(2.10.1): MEGA downloads, Drive shortcut download/size fixes, nat…

FDM v2.10.0

ci: ffmpeg sidecar fetch retries + arm64 fallback mirror

The macOS release build fetches static ffmpeg/ffprobe only from
martin-riedl.de, which returned HTTP 521 (origin down) for the v2.10.0
build. Add exponential-backoff retries and an osxexperts.net fallback
for arm64 so one mirror being down no longer fails the release.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

FDM v2.9.2

fix(2.9.2): tolerate slow rqbit first-spawn ("HTTP API did not come up")

- Widen the rqbit API startup wait from ~5s to ~30s. The first spawn right after
  an app update is slow because macOS Gatekeeper (and Windows Defender) re-scans
  the freshly-written rqbit binary; the short timeout surfaced a spurious
  "rqbit HTTP API did not come up" and blocked the torrent.
- Classify that error (and other rqbit/torrent-engine startup hiccups) as a
  transient network kind so it auto-retries with backoff instead of waiting on a
  manual Retry.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

FDM v2.9.1

fix(2.9.1): document-style file preview, native YT icon, clearer ext …

FDM v2.9.0

feat(2.9.0): file preview revamp + ZIP/RAR extractor, open-completed,…

FDM v2.8.9

feat(2.8.9): extension filename + single-prompt capture, no rubber-ba…

FDM v2.8.8

feat(2.8.8): torrent DHT persistence + live peer counts

- Enable rqbit DHT persistence (drop --disable-dht-persistence) so the routing
  table is cached between runs — faster peer discovery for magnets instead of a
  cold DHT bootstrap every launch.
- Surface live peer counts: rqbit peer_stats.live → TStats.peers → NativeHandles
  → JobStatus.peers → UI. The dock shows "Connecting… · N peers" (or "· N peers"
  once downloading), and the Transfers table shows "Connecting…" for a torrent
  still resolving metadata plus a Peers stat in the info panel — so a dead/
  unseeded torrent reads clearly instead of a misleading "Downloading 0%".

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

FDM v2.8.7

feat(2.8.7): magnet OS handler + self-healing torrent engine

Magnet deep links
- Registered FDM as the OS handler for magnet: links via tauri-plugin-deep-link
  (scheme in tauri.conf.json, deep-link:default capability). Clicking a magnet in
  a browser opens FDM and queues the torrent.
- Handles every entry path: macOS Apple-event (running + cold launch), Windows/
  Linux argv, and single-instance forwarding. Rust buffers links (PendingMagnets)
  + emits open-magnet; the frontend drains any launch links via take_pending_magnets
  and listens live, queuing into the default download folder.

Torrent engine self-heals
- rqbit's cached API base was reused with no liveness check, so once the sidecar
  died every add/stats failed with "error sending request" and the graceful retry
  looped forever. ensure() now probes the cached engine and respawns a fresh rqbit
  if it isn't answering.

Note: the magnet scheme registers with the OS only in an installed/bundled build
(macOS Info.plist CFBundleURLTypes); dev doesn't register it, Windows is CI-gated.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

FDM v2.8.6

feat(2.8.6): app-wide Shared Drive dock, docked transfer tab, recents…

FDM v2.8.5

feat(2.8.5): graceful transfer failure, multi-select, recent-folders …