Pinning services can remove their own copy of a file. They cannot remove it from IPFS. Here is exactly what a takedown does and does not accomplish.

libp2p connections can run over more than one transport. Here is exactly what changes with QUIC instead of TCP, and why IPFS dials both at once.

The DHT answers who has a CID. GossipSub answers a different question: how do peers push real-time updates to everyone listening, without a lookup at all.

js-ipfs is deprecated. Helia is what replaced it: a modular, TypeScript-first IPFS implementation built for the browser and Node.js. Here is how it fits.

Not every retrieval needs the whole DAG. IPLD Selectors describe exactly which nodes to traverse and match, so a client can fetch a slice, not everything.

Almost no browser understands ipfs:// links natively. Here is exactly why, what IPFS Companion actually does about it, and why gateway URLs took over instead.

IPFS private networks use a shared secret, a swarm key, to restrict which peers can connect at all. Here is how it works, and how it differs from pinning.

A single node either pins a file or it doesn't. Here is the general pattern multi-node pinning services use instead: replication factors and allocation.

A CAR file packages an entire IPFS DAG, blocks and all, into one portable archive. Here is exactly how the format works and why it exists at all.

Bitswap has no payment system, so how does it stop freeloaders? Each peer keeps a ledger and a debt ratio, and gets stingier with peers who never give back.

IPLD is the general data model that makes IPFS's Merkle DAG work for more than files. Here is how the Data Model, codecs, and multicodecs actually fit together.

Being pinned is not the same as being findable. IPFS provider records expire, and nodes have to keep re-announcing content to the DHT to stay discoverable.