Note: Links on this page use the anonym.to service.
muddying the waters of the digital copyright debate
Monolith is a simple tool that takes two arbitrary binary files (called a Basis file and an Element file) and "munges" them together to produce a Mono binary file (with a .monoextension). Monolith can also reconstruct an Element file from a Basis file and a Mono file.
In most cases, the resulting Mono file will not be statistically related to either file. If you compare the Mono file to the Element file, the Mono file will contain none of the information present in the Element file. In other words, the Mono file by itself tells you nothing at all about the data in the Element file. Only when combined with the Basis file will the Mono file provide information about the Element file.
Monolith can be used for exploring the boundaries of digital copyright, and the rest of this website is devoted to such an exploration. The core questions: What happens when we use Monolith to munge copyrighted files? What is the copyright status of the resulting .mono file?
These questions are considered in the Official website (includes download links): http://monolith.sourceforge.net/
Monolith was developed on a lark. It is a philosophical experiment, a curiosity, and perhaps even a hare-brained scheme. In any case, Monolith is meant to stir debate: a perfect, flawless system would not stir debate very well, would it? Monolith exists comfortably in a world of logical gymnastics. The real world of copyright does not operate in a logical fashion. Thus, a word of warning: if you apply Monolith in the real world, your legal mileage may vary.
Plus see note on OFF System