News for hackers. Stuff that matters.
Re:Putting 5,998,794 books on IPFS by Gigachad on Saturday November 19, 2022 @05:36PM (#33675568)
I’ve been interested in IPFS for a while now but I’m still unable to come up with a good explanation of how it’s different to regular torrents. Does anyone have any examples of stuff you can do with IPFS that you can’t with torrents?

Seems like over the last 5 years they haven’t really done anything but add crypto buzzwords to the project site.

Re:Putting 5,998,794 books on IPFS by rudolph9 on Saturday November 19, 2022 @05:40PM (#33675630)
The content is the address, no central issuer of the tracker file needed just the CID content ID. Also since the CID is a hash of the data it can be used to validate the data :wink:
Re:Putting 5,998,794 books on IPFS by nodja on Saturday November 19, 2022 @05:46PM (#33675683)
That is exactly how bittorrent works as well tho. Bittorrent hasn't needed any trackers for public torrents since 2005 and can work solely off magnet links using the DHT network. Just like how IPFS does it.
Re:Putting 5,998,794 books on IPFS by yellowsir on Sunday November 20, 2022 @07:34AM (#33680430)
the difference is, when you have a lot of (small) files. With ipfs you have one global peer pool, with torrents you need a pool per file.
Re:Putting 5,998,794 books on IPFS by teraflop on Saturday November 19, 2022 @05:47PM (#33675694)
That's basically the same as torrents with magnet links.

As other commenters pointed out, the biggest real difference is that IPFS objects can cross-reference each other by hash, which allows you to do partial updates.

Re:Putting 5,998,794 books on IPFS by layer8 on Saturday November 19, 2022 @05:54PM (#33675774)
An “update” means a new CID though, and this basically works like a persistent data structure [0]?

[0] https://en.wikipedia.org/wiki/Persistent_data_structure

Re:Putting 5,998,794 books on IPFS by bakugo on Saturday November 19, 2022 @05:48PM (#33675709)
That's quite literally how bittorrent with DHT works. To download a public torrent you only need its content hash, the metadata and peers are then fetched via DHT assuming at least one reachable DHT node is aware of the torrent.
Re:Putting 5,998,794 books on IPFS by fomine3 on Sunday November 20, 2022 @09:26PM (#33687943)
Winny (since 2002) and successor Japanese P2P network were like that. They use MD5/SHA file hash as address. https://en.wikipedia.org/wiki/Winny
Re:Putting 5,998,794 books on IPFS by georgyo on Saturday November 19, 2022 @05:44PM (#33675658)
The biggest thing is that in IPFS each chunk has a CID, and that CID is globally unique and sharable from other CIDs.

You can think of each CID as a mangent link, and each CID can point to more CIDs.

Where as in a torrent the peer tracking is done at the whole torrent level, instead of the chunks inside the torrent.

Torrent V2[0], which has poor adoption thus far, should also allow for a similar ability. To my knowledge this is not being taken advantage of yet.

[0]: https://blog.libtorrent.org/2020/09/bittorrent-v2/

Re:Putting 5,998,794 books on IPFS by mdp2021 on Saturday November 19, 2022 @06:58PM (#33676399)
> each chunk has a CID

An extremely interesting problem, fingerprinting generic binary - reducing kilobytes and megabytes into a handful of bytes, and avoiding collision.

Much simpler on large data.