The main thing IPFS does better (in my opinion) is that the user interface is based around "browsing web sites" instead of "downloading files". For example, you can upload all of Wikipedia to IPFS such that users can easily read specific articles they're interested in without downloading the whole thing.
I think this is mostly a UI thing, not an improvement to the underlying technology. IIRC it's technically possible to "stream" from torrents or download chunks of them, it's just not the default way people interact with them.
IPFS is a HTTP replacement much more than it is a BT replacement. Meaning it provides namespace to access and link content, but unlike HTTP that is build around server addresses, IPFS build around content addressing. Another big advantage IPFS has over HTTP is that it supports directories natively, thus making the use of archive files largely unnecessary (in theory it could also be extended to address files inside archives directly, so that's not implemented I think).
In theory that allows some extremely powerful things, such as making all the content of the world part of your filesystem. You can just "cd /ipfs/<long hash>/" and browse around whatever directory tree you are interested in. It completely bypasses the need to manually download anything, as you can access the data directly under a globally unique name.
IPFS is also much more suited for small files, so you could use it to host individual .jpg files, something that would be rather unwieldy with torrent.
In actual use however it barely works, it's slow, it's eats lots of CPU even when doing nothing and the fuse plugin to integrate it into your filesystem is also rather broken. POSIX file io is also ill suited for this kind of transparent file access, so all your apps will just freeze without any indication what is going on if you try to use the /ipfs/ directory.
Another huge problem with IPFS is the complete lack of authorship/copyright tracking. HTTP has that implicitly, since whoever hosts the content is responsible for it. With something like IPFS however you automatically become hoster for everything you look at. I can't see that working in the current legal system. Even distributing Open Source projects via IPFS is already illegal, as the LICENSE.txt you are generally required to redistribute no longer is linked with the actual rest of the source code once you can address and cache each file, or even blocks within a file, individually. If IPFS would ever become popular it would be quickly made unusable by lawyers, as unlike torrent, you downloading is not an active act here, it just happens in the background.
csande17|2 years ago
I think this is mostly a UI thing, not an improvement to the underlying technology. IIRC it's technically possible to "stream" from torrents or download chunks of them, it's just not the default way people interact with them.
grumbel|2 years ago
In theory that allows some extremely powerful things, such as making all the content of the world part of your filesystem. You can just "cd /ipfs/<long hash>/" and browse around whatever directory tree you are interested in. It completely bypasses the need to manually download anything, as you can access the data directly under a globally unique name.
IPFS is also much more suited for small files, so you could use it to host individual .jpg files, something that would be rather unwieldy with torrent.
In actual use however it barely works, it's slow, it's eats lots of CPU even when doing nothing and the fuse plugin to integrate it into your filesystem is also rather broken. POSIX file io is also ill suited for this kind of transparent file access, so all your apps will just freeze without any indication what is going on if you try to use the /ipfs/ directory.
Another huge problem with IPFS is the complete lack of authorship/copyright tracking. HTTP has that implicitly, since whoever hosts the content is responsible for it. With something like IPFS however you automatically become hoster for everything you look at. I can't see that working in the current legal system. Even distributing Open Source projects via IPFS is already illegal, as the LICENSE.txt you are generally required to redistribute no longer is linked with the actual rest of the source code once you can address and cache each file, or even blocks within a file, individually. If IPFS would ever become popular it would be quickly made unusable by lawyers, as unlike torrent, you downloading is not an active act here, it just happens in the background.