zlacker

It's possible that the source sharded the torrent payload and then distributed the shards among multiple "seeds" that are brought online/offline on a rolling schedule, to avoid being identified as the lone seed. Since none of the "seeds" have the entire payload, they are identified as peers (specifically, leechers) in the torrent client.

>>common+(OP)
This 30+ MB torrent file is choking ruTorrent and Deluge clients on my seedbox. Not sure how to fix it. Do you know of some alternative way to process such a large file? I have never seen such a large torrent file like this before.

>>nebula+63
The screenshot from one of the replies to the tweet (https://twitter.com/pompompur_in/status/1437905607273635847) seems to be of qBittorrent. It's open source and cross-platform, just like Deluge.

https://www.qbittorrent.org/download.php

>>common+k3
Not available on my server unfortunately. Otherwise qBitorrent is the client of choice. I have found magnet links from DdosSecrets here: https://ddosecrets.com/wiki/Epik

Edit: Turns out I didn't give enough attention to Transmission as it handled the file. Very impressive.

As a side note: this has got me pondering about testing edge cases on open source software. Wonder how much of that actually gets done.

>>nebula+63
rtorrent has handled literally _everything_ I've ever thrown at it

>>cheeze+F4
It didn't handle this one when I tried it.