2004 · a single protocol with no company, no datacenters, no servers behind it
capacity fixed vs. capacity that grows with demand — the inversion, still in production today
the three artifacts every other mechanism builds on
download anything and you become a peer — an equal, by design
each one is a technique you can lift into your own systems
to distribute a file in 2001: host it, and pray — cost scales with users, capacity doesn’t
not a setting — a property of the protocol · downloading makes you a distributor
slice the file → thousands of concurrent sources · a download becomes an upload in seconds
you can’t authenticate anonymous peers — so the data has to prove itself
piece 1, 2, 3… feels natural — and kills the swarm in three separate ways
every client optimizes swarm health — which turns out to equal its own speed
the last blocks get requested from everyone — first arrival wins, the rest are cancelled
uploading costs money — so the rational move is: download everything, upload nothing
choking: upload fast and neighbors reciprocate — upload nothing and the swarm freezes you out
pure tit-for-tat can’t admit newcomers — one random slot every 30 s fixes the bootstrap
as of 2005: a legal single point of failure as much as a technical one — trackers kept vanishing
2005: Mainline DHT — a hash table with no table server · nodes and torrents share one 160-bit ruler
content addressing all the way down — no site, no file, just the fingerprint
the architecture underneath flipped: from addressing a place to addressing the data itself
why torrents used to wreck your video calls — and it wasn’t about raw bandwidth
≈2009: stop waiting for packet loss — measure queueing delay and yield like a background task
when demand is the load, demand is also the fleet
every consequence has a shadow — know which ones you inherit before you borrow the pattern
none of these require a P2P network — they’re design moves
six mechanisms, one property — a protocol with no company carried a third of the internet