4 ms·

That might be how some client(s) work, but I don't think that is how IPFS works. If you access a piece of content over ipfs.io for example, I would think you j

• jacooper 3y ago
  Because its using a gateway. I think if you are accessing it natively through IPFS, it will default to adding you as a peer.
  • TekMol 3y ago
    That would hold true if IPFS would be a specific application. But it is a protocol. I would not expect that the protocol specifies that a complient client shares what it downloaded. That sounds more like a choice the client developers make on their own. But I'm happy to be corrected if someone has a link to the protocol definition and it says different.
    • nightpool 3y ago
      By default, what the GP says is true. If you can point to specific popular clients that do not have that behavior by default then I think that would be more convincing than saying "Well technically there's no requirement" when it's impossible to avoid in practice without writing your own custom implementation from scratch
      • wuiheerfoj 3y ago
        Afaiu, [Lassie](https://github.com/filecoin-project/lassie/ https://github.com/filecoin-project/lassie/) is the latest and greatest of IPFS clients and it does not store/provide any data that you access
        • rahimnathwani 3y ago
          AIUI Lassie uses indexers to locate content instead of using a distributed hash table (DHT). So a content identifier (CID) might be present on IPFS (and downloadable by a regular IPFS client), yet 'invisible' to Lassie. If my understanding is correct, it can't be considered a complete IPFS client. https://docs.filecoin.io/storage-provider/architecture/network-indexer/ https://docs.filecoin.io/storage-provider/architecture/netwo... https://en.wikipedia.org/wiki/Kademlia https://en.wikipedia.org/wiki/Kademlia
          • wuiheerfoj 3y ago
            I think it uses indexer and saturn (which ought to fall back to the DHT if it hasn’t cached the content of a CID already). That said they have a GitHub issue tracking CIDs that are retrievable via Kubo (fka go-ipfs) that aren’t yet retrievable via Lassie - it suggests to your point that there must be some difference; it also suggests they intend for retrievability parity though, so fingers crossed!!
            • rahimnathwani 3y ago
              This issue, right? https://github.com/filecoin-project/lassie/issues/136 https://github.com/filecoin-project/lassie/issues/136
  • kkielhofner 3y ago
    Yes and the many IPFS implementations (I've tried them all) consume tremendous amounts of bandwidth and require shocking levels of system resources (considering what it does fundamentally). There's an entire cottage industry of IPFS pinning and gateway providers that exist largely because of the challenges of running your own IPFS node for anything beyond casual use.
    • somat 3y ago
      Ipfs is is a neat project with a lot of interesting ideas. but, yeah, the deamon is often way too resource hungry. I would like to see a lite/embedded mode that would better run in resource constrained or casual setups.
• gkbrk 3y ago
  If you access a piece of content over ipfs.io, and you don't have your browser set up to actually do those requests over a local IPFS daemon, you are not using IPFS. You are just using a normal centralized website.