In the now-fading lexicon of Web 2.0, certain project names carry the weight of a what-if. BurnBit is one of them. For the uninitiated, BurnBit (circa 2009–2012) was a radical web service that allowed users to generate a BitTorrent file from any standard HTTP URL. If you found a file on a slow server—a Linux ISO, a forgotten indie game, a public domain film—BurnBit would "burn" it into a torrent, creating a magnet link where none existed.
Every time a link rots (HTTP 404), every time a cloud provider raises egress fees, the ghost of BurnBit whispers: There was another way. You could have burned it. burnbit experimental
But the experiment succeeded. Elements of its design live on in IPFS (InterPlanetary File System), in WebTorrent, and in the lazy-loading CDN strategies of modern cloud providers. When you watch a video served from a peer-assisted CDN like Peer5, you are using a polished, corporate version of the BurnBit experimental stack. To call something "experimental" is to admit it might fail. BurnBit failed as a service, but as an experiment, it illuminated the exact tension we still live with: the tension between the open, resilient, messy P2P web and the fast, controlled, fragile corporate web. In the now-fading lexicon of Web 2