3 ms·
I realize this portion isn't the focus but it caught me a bit off guard: "Due to its size, it's incompatible with most torrent clients and many users will have
by zamadatix 5y ago
I realize this portion isn't the focus but it caught me a bit off guard:
"Due to its size, it's incompatible with most torrent clients and many users will have difficulty downloading the data. When we're able, we'll release a more accessible version of the data."
As someone who downloads a lot of 4k HDR... Linux ISOs... (I have the highest level subscriptions to Disney+, Netflix, Hulu, HBO, Spotify, Amazon, Crunchyroll, and probably more I'm forgetting but not all of my devices will get the 4k stream due to DRM requirements so depending where I want to watch it I'll just download it instead) I've tried about every popular torrent client I've heard of and none have had problems with 100 GB+ sized torrents (or even much larger). Is this really a thing or are a lot of people just using a 10 year outdated version of uTorrent or something?
- techrat 5y agoIt might be the number of files and subdirectories rather than the total file size of the torrent.
- bikezen 5y agoThats the size of the actual .torrent file, all the metadata. Not the size of the data the torrent is pointing to.
- zamadatix 5y agoApart from the hilarity of the idea there are multiple petabytes of data in this leak - no, the torrent file was actually pretty small. About the size you'd expect for 180 GB of payload with a decent number of files.
- generalizations 5y agoThe torrent file is 32Mb. That's really big for a torrent file, and it made my deluge client choke.
- deleted 5y ago[deleted]
- MrStonedOne 5y agothe actual .torrent file, itself, is 32mb, this is massively bigger then your 2tb 40 files 4k movie superpack, because this includes large directories and file paths as well as a larger number of files, each requiring the full file path be specified.
- sneedus 5y agotried deluge and qbit qbit loaded it instantly while deluge froze for like 15 minutes