Burnbit became a tool for copyright infringement obfuscation. Users would take a direct download link from a file locker (like RapidShare or Megaupload) and convert it to a torrent.
This was the wildest feature. The experimental branch allowed you to paste two different URLs for the same logical file.
For example, suppose a movie was split into Part 1 on MegaUpload and Part 2 on RapidShare. The experimental Burnbit would generate a single torrent that told BitTorrent clients: burnbit experimental
The BitTorrent client would then open two parallel HTTP streams, download the pieces, and reassemble them on the fly. To the user, it looked like a single torrent. To the lawyers, it was a nightmare. This "experiment" lasted roughly six months before the hosting providers started sending cease & desist letters.
The holy grail of experimental torrenting is Erasure Coding. Standard torrents fail if you lose specific pieces. Experimental BurnBit could generate a torrent where you only need 70 out of 100 pieces to reconstruct 100% of the data (similar to ZFS or RAID). Burnbit became a tool for copyright infringement obfuscation
Before diving into the experimental lab, let’s establish the baseline. Burnbit, launched in the late 2000s, acted as a proxy between the centralized web and the decentralized BitTorrent network.
The Standard Workflow:
Essentially, Burnbit was a "super-seeder." It allowed a file that was sitting lonely on a slow web server to become a torrent with a healthy initial seed. This was revolutionary for sharing large datasets, old software, or creative commons media.
BitTorrent assumes chunks are immutable. The experimental dynamic proxy sometimes served stale data. If the original HTTP file updated while a torrent was active, peers would get hash failures and ban each other. The swarm collapsed into chaos. The BitTorrent client would then open two parallel
