Mono - Revision history

Zzo38: Add format description

2021-01-15T00:31:01Z

Add format description

Jsummers at 22:04, 4 June 2017

2017-06-04T22:04:29Z

Dan Tobias at 03:58, 4 April 2016

2016-04-04T03:58:05Z

Dan Tobias: Created page with "{{FormatInfo |subcat=Error detection and correction |extensions={{ext|mono}} |released=2004 }} '''Mono''' files can be seen as a sort of parity file to check the integrity of ..."

2016-04-04T03:56:38Z

Created page with "{{FormatInfo |subcat=Error detection and correction |extensions={{ext|mono}} |released=2004 }} '''Mono''' files can be seen as a sort of parity file to check the integrity of ..."

New page

{{FormatInfo
|subcat=Error detection and correction
|extensions={{ext|mono}}
|released=2004
}}
'''Mono''' files can be seen as a sort of parity file to check the integrity of a file, or as a form of encoding for a file allowing it to be recovered. The format seems to have been created primarily to tweak the noses of copyright enforcers by creating a philosophical dilemma as to whether a file is truly infringing if it is derived from a copyrighted work, and can be restored to a full copy of it, but by itself has no part of the copyrighted item (and, by suitable manipulation of the "basis" file used to encode it, can even be made to be identical to a totally different meaningful file, copyrighted by somebody else or public-domain).

A Mono file is created from two other files, a "basis" file used as a key, and an "element" file that is the source data. It is generated by a bit-by-bit XOR operation, with the basis file being repeated as needed to equal the length of the element file.

== Links ==
* [http://monolith.cvs.sourceforge.net/viewvc/monolith/Monolith/doc/monoFileFormat.txt?revision=HEAD Format description]
* [http://monolith.sourceforge.net/ Official site wtih discussion and software download]

← Older revision		Revision as of 00:31, 15 January 2021
Line 7:		Line 7:

	A Mono file is created from two other files, a "basis" file used as a key, and an "element" file that is the source data. It is generated by a bit-by-bit [[Exclusive Or\|XOR]] operation, with the basis file being repeated as needed to equal the length of the element file.		A Mono file is created from two other files, a "basis" file used as a key, and an "element" file that is the source data. It is generated by a bit-by-bit [[Exclusive Or\|XOR]] operation, with the basis file being repeated as needed to equal the length of the element file.
		+
		+	== Format description ==
		+	The data is simply the data of two others files (described above) XORed together, and has the same length as the element file. The name of the file is the names of the two original files with <tt>-#-</tt> in between, and then <tt>-#-.mono</tt> at the end. Neither original file name is allowed to have <tt>-#-</tt> in it.

	== Links ==		== Links ==

@@ Line 6: / Line 6: @@
 '''Mono''' files can be seen as a sort of parity file to check the integrity of a file, or as a form of encoding for a file allowing it to be recovered. The format seems to have been created primarily to tweak the noses of copyright enforcers by creating a philosophical dilemma as to whether a file is truly infringing if it is derived from a copyrighted work, and can be restored to a full copy of it, but by itself has no part of the copyrighted item (and, by suitable manipulation of the "basis" file used to encode it, can even be made to be identical to a totally different meaningful file, copyrighted by somebody else or public-domain). The Monolith tool is used to create them.
-A Mono file is created from two other files, a "basis" file used as a key, and an "element" file that is the source data. It is generated by a bit-by-bit XOR operation, with the basis file being repeated as needed to equal the length of the element file.
+A Mono file is created from two other files, a "basis" file used as a key, and an "element" file that is the source data. It is generated by a bit-by-bit [[Exclusive Or|XOR]] operation, with the basis file being repeated as needed to equal the length of the element file.
 == Links ==

@@ Line 4: / Line 4: @@
 |released=2004
 }}
-'''Mono''' files can be seen as a sort of parity file to check the integrity of a file, or as a form of encoding for a file allowing it to be recovered. The format seems to have been created primarily to tweak the noses of copyright enforcers by creating a philosophical dilemma as to whether a file is truly infringing if it is derived from a copyrighted work, and can be restored to a full copy of it, but by itself has no part of the copyrighted item (and, by suitable manipulation of the "basis" file used to encode it, can even be made to be identical to a totally different meaningful file, copyrighted by somebody else or public-domain).
+'''Mono''' files can be seen as a sort of parity file to check the integrity of a file, or as a form of encoding for a file allowing it to be recovered. The format seems to have been created primarily to tweak the noses of copyright enforcers by creating a philosophical dilemma as to whether a file is truly infringing if it is derived from a copyrighted work, and can be restored to a full copy of it, but by itself has no part of the copyrighted item (and, by suitable manipulation of the "basis" file used to encode it, can even be made to be identical to a totally different meaningful file, copyrighted by somebody else or public-domain). The Monolith tool is used to create them.
 A Mono file is created from two other files, a "basis" file used as a key, and an "element" file that is the source data. It is generated by a bit-by-bit XOR operation, with the basis file being repeated as needed to equal the length of the element file.
@@ Line 11: / Line 11: @@
 * [http://monolith.cvs.sourceforge.net/viewvc/monolith/Monolith/doc/monoFileFormat.txt?revision=HEAD Format description]
 * [http://monolith.sourceforge.net/ Official site wtih discussion and software download]