Worth noting if someone uses this to share private data: Checking the "Private torrent" would tell your and compliant clients to not use DHT and other public methods that can leak the content. But it doesn't stop other non-compliant clients from sharing it on the DHT once they have it, nor does it stop someone from just ticking "Enable DHT" on their side once they have received it (or change "private" to "false" in the torrent file itself).<p>Obvious to many I'm sure, but maybe best to be explicit about it anyways.<p>Slightly off-topic but kind of fitting: How does infohash v2 support look like today? It's been available for years, but seemingly most private trackers + most other places seems to still be using v1. What clients are people using today, do those support v2? As far as I know, all modern clients do, so it would be possible to start using v2 exclusively.<p>Reason for the question is that I'm planning to distribute many large files to the public, and in my experience, BitTorrent works really well for that. Question is if it's enough to just publish v2 infohashes, or I need to publish both v1 and v2.
Love this. I continue to believe Torrenting is the best way to share files, particularly big files, rather than uploading them to some cloud instance with questionable privacy policies…
Is there a self-hostable BitTorrent tracker that can run with Docker? I know there's an option on qBittorrent but I don't want my server to run a full BitTorrent client; just the tracker.
For the less technically inclined folks that don't trust this hosted service or can't host their own it's probably simpler to just use a seedbox if you need to access torrented files from multiple locations or you want to share them with others.