> usenet | binary | efficient <
// yEnc - Efficient 8-bit binary encoding for Usenet and email
Low Overhead
Only 1-2% encoding overhead compared to 33% for Base64.
Error Detection
Built-in CRC32 checksums ensure data integrity.
8-bit Clean
Designed for 8-bit transport systems like modern email and Usenet.
>> technical info
How yEnc Works:
yEnc adds 42 to each byte value (modulo 256) and escapes special characters. This simple transformation allows efficient binary transmission through 8-bit clean channels with minimal overhead.
Example:
Binary data → =ybegin... Encoded data =yend crc32=...
Why Use yEnc:
- >Usenet binary posting
- >Email attachments
- >Efficient file transfer
- >Low bandwidth overhead
- >Built-in error checking
>> frequently asked questions
What is yEnc?
yEnc is a binary-to-text encoding scheme designed for transferring binary files over Usenet. It's much more efficient than UUencoding or Base64, with only 1-2% overhead.
How efficient is yEnc compared to other encodings?
yEnc has only 1-2% overhead compared to 33% for Base64 and 37% for UUencoding. This makes it ideal for large binary files on bandwidth-limited systems.
Why was yEnc created?
yEnc was created in 2001 to replace inefficient encodings like UUencode on Usenet, taking advantage of modern 8-bit clean transport systems.
What are the special characters in yEnc?
yEnc escapes NULL (0x00), LF (0x0A), CR (0x0D), space (0x20), tab (0x09), and equals (0x3D) by prefixing them with = and adding 64 to their value.
Other Languages
References
How we make sure
We check this tool with the automated test suites linked below. Example checks are shown in their original language.
- Verification method
- Independently undo escaped byte shifts and compare the trailer CRC-32 with Python.
- Comparison reference
- Python standard-library zlib.crc32 and explicit byte-arithmetic assertions.
- Verification scope
- These samples and boundaries do not prove correctness for every input.
Test source and cases (select a file to read it)
-
text-reliability.test.js
- yEnc: payload shift and CRC-32 trailer agree with independent Python zlib
These checks cover the listed examples and boundaries, not every possible input. Round trips and checks using the same library are not independent verification.