Wouldn't IPFS make it easier to access individual files compared to a Torrent file?
26TB is a massive amount of data.
Having downloaded (very) large dumps in the past with torrents, I've found it always a bit annoying especially when attempting to access a subset, torrent client interfaces are less than ideal here. Not that someone can't build a good document browser on top of torrents - ala those movie torrent streaming apps.
I'm not familiar with how IPFS works in detail but being able to access it via a file system sounds much better UX wise. Hopefully it can support that scale.
But to your point the primary end-goal of "censorship-free" persistent access is largely the same AFAIK.
You don't have to download an entire torrent to access a single file. Most torrent client can prioritize files so they get downloaded first, or avoid downloading everything in favor of just one or two. That is, unless the torrent is just a single zip or something.
Yes I mentioned that in my comment but it's not an ideal (or even practical) interface when you have 26TB of files. You'd have to build a special torrent interface to deal with that in a useful way. Existing torrent clients are far from capable of handling this meaningfully.
and if everyone does that, noone will offer the particular file except hosts, so the availabilty can be spotty - and the torrent interfaces have no way to tell upfront.
26TB is a massive amount of data.
Having downloaded (very) large dumps in the past with torrents, I've found it always a bit annoying especially when attempting to access a subset, torrent client interfaces are less than ideal here. Not that someone can't build a good document browser on top of torrents - ala those movie torrent streaming apps.
I'm not familiar with how IPFS works in detail but being able to access it via a file system sounds much better UX wise. Hopefully it can support that scale.
But to your point the primary end-goal of "censorship-free" persistent access is largely the same AFAIK.