Not quite. It let's you seed two or more different torrents that have the same (bit-identical) media file, and automatically merges and cross-shares the chunks between them. Even if there's no seeders on each individual torrent, it's feasible to combine the downloading power to get them completed and become the seeder. Done it many times and works pretty well.

I prefer scene releases as there's a decent quality version in whatever resolution for practically everything - and being properly tagged you can usually find the exact file on places like Usenet/IRC. One trick I use is to search in BiglyBT for the exact file size in bytes as per srrdb, and it often comes up with something (sometimes even several torrents with no seeds that can be swarm merged).

smartctl --scan | awk '{print $1}' | xargs -I {} sh -c 'echo -n "{}: "; smartctl -A {} | awk "/Power_On_Hours/ {printf \"%.2f years\n\", \$10/8760}"'

/dev/sda: 0.30 years #14TB WD Elements (shucked)
/dev/sdb: 2.64 years #8TB WD My Book (shucked)
/dev/sdc: 12.37 years #3TB WD Red
/dev/sdd: 2.86 years #12TB My Book (shucked)
/dev/sde: 13.47 years #3TB WD Red
/dev/sdf: 1.26 years #14TB WD Elements (shucked)
/dev/sdg: 10.55 years #5TB WD Red

Most of these drives served on Windows Server bare metal w/ StableBit DrivePool + SnapRAID before migrating to Proxmox mergerfs + SnapRAID & ZFS. My raidz1 pool has a combine total of 36+ years lol. Yes I do have backups. :)

Duplicacy has a -nobackup-file option, documented with the set cmd.

Some of your other info about Duplicacy is very obviously wrong or out-of-date. Stop relying on AI for research. :)

Get a VPN with port forwarding. Problem solved.

Plex was running on his private computer, not a dedicated server, right?

They opened it to the internet - that's the big difference (and the topic at hand). Security is a multi-layered thing, but if your weakest point is a gaping hole, the rest doesn't mean much. To my point - assuming Jellyfin ain't gonna have vulnerabilities even when you're fully up-to-date, is foolhardy.

Yea I haven't tried Pangolin myself - looks a bit bloated for my tastes, but I have tried rinetd across Tailscale and it worked brilliantly (very simple conf file), and I've done reverse ssh before (using autossh) which was a bit fiddly. frp does look promising though, just as a VPS<->home bridge.

I mean, anything with a web server can have vulnerabilities. Just look at the LastPass breach where hackers got in through an employee's exposed Plex library.

This video addresses many of the concerns of hosting stuff in public, and details a way (and some tools) to do it relatively securely. (There's always a risk there'll be a zero-day vulnerability in a web application like Jellyfin, but you can mitigate against them if you use the right strategies/tools, and you're vigilant enough.)

Since you're on cgnat, you can set up Pangolin on a VPS, or Tailscale-->rinetd-->Tailscale tunnel, also on a VPS. (Apparently frp is another similar solution, with p2p proxying.)

MURDERER!

FXP

Oh wow, there's a name I ain't heard in a while.

Fantastic rebuttal kindergartener, you convinced everyone.