Codegroup project, volunteer coders needed

Message boards : Science (non-SETI) : Codegroup project, volunteer coders needed
Message board moderation

To post messages, you must log in.

Volunteer tester

Send message
Joined: 22 May 99
Posts: 29
Credit: 152,726
RAC: 73
New Zealand
Message 1067554 - Posted: 17 Jan 2011, 4:45:12 UTC
Last modified: 17 Jan 2011, 4:53:43 UTC

As cryptography and information theory are tied into Deep Space Telecom, this project may be of some interest to some of you who code Java. Many fixes are needed for the project to become useful, as in its current form it has limited utility.

Codegroup project, volunteer coders needed

codegroup encodes any file into this form, allowing it to be transmitted through any medium, and decodes files containing codegroups into the original input. Encoded files contain a 16-bit cyclical redundancy check (CRC) and file size to verify, when decoded, that the message is complete and correct. Files being decoded may contain other information before and after the codegroups, allowing in-the-clear annotations to be included.

codegroup makes no attempt, on its own, to prevent your message from being read. Cryptographic security should be delegated to a package intended for that purpose, such as pgp. codegroup can then be applied to the encrypted binary output, transforming it into easily transmitted text. Text created by codegroup uses only upper case ASCII letters and spaces. Unlike files encoded with uuencode or pgp's “ASCII armour” facility, the output of codegroup can be easily (albeit tediously) read over the telephone, broadcast by shortwave radio to agents in the field, or sent by telegram, telex, or Morse code.

Only codegroup conforms to the telegraphic convention of all upper case letters, and passes the “telephone test” of being readable without any modifiers such as “capital” and “lower-case”. Avoiding punctuation marks and lower case letters makes the output of codegroup much easier to transmit over a voice or traditional telegraphic link.

BUGS : When a CRC error is detected, no indication is given of the location in the file where the error(s) occurred. When sending large files, you may want to break them into pieces with the splits utility so, in case of error, only the erroneous pieces need to be re-sent.

BUGS : It would be nice to embed the original file name and modes in the encoded output, but this opens the door to all kinds of system-dependent problems. You can always include this information as text before the first codegroup, or send an archive created with tar or zip.
ID: 1067554 · Report as offensive
Profile ML1
Volunteer tester

Send message
Joined: 25 Nov 01
Posts: 9349
Credit: 6,858,887
RAC: 2,195
United Kingdom
Message 1068026 - Posted: 18 Jan 2011, 21:18:49 UTC - in response to Message 1067554.  


What's 'special' about the project and the 'codegroups' that isn't already done elsewhere?

Keep searchin',

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)
ID: 1068026 · Report as offensive

Message boards : Science (non-SETI) : Codegroup project, volunteer coders needed

©2017 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.