Yenc Compression - Wow!

[d1abolic]

Amazing. I was just downloading Jedi Knight II when i realised that the 15MB rars i just downloaded were actually 5MB downloads. Unbelievable!

 

[chrisjor]

why do they need to be rar'd and yenc encoded? I was downloading a pr0n I wanted, and one of the rar's was corrupt, so I could not get the archive open. I only wanted to see the first scene, and the corrupt file was one of the last. If it had been left as an .mpg and only yEnc encoded, I would have been able to watch the first scene (good girl/girl action!!!).

 

[Czar]

whats yenc?

 

[FrontlineWarrior]

yenc is some sort of compression/protocol or something on newsgroup binaries. it's supposed to check file integrity and reduce overhead in size. it makes no difference as far as i could tell.

 

[d1abolic]

It does. I had to download files from two different groups, so i know. One had Yenc, other didn. Files were 110,000 lines in the first and over 300,000 lines in the second. First i thought they were corrupt, but i downloaded and they work fine. Really 15MB. But download 3x faster.

 

[PliotronX]

Info @ /.

 

[royaldank]

yenc looks pretty good. However, I just got the new Agent 1.91 last night, so I haven't been able to see the difference yet. However, the lines in the files are drastically different. About a third the size of regularly encoded files.

 

[GL]

Yenc isn't compression. It is really an encoding technique. It appears like it is compression because Yenc encoded binaries are typically 30-40% smaller than other usenet binaries. Apparently, traditional usenet binary encoding techniques involve quite a bit of bloat in order to satisfy old news servers by producing 7-bit data. Essentially, they inflate original binaries so that they can be properly stored on news servers. UPDATE: Should've read PliotronX's link, I just provided the same one

 

[GagHalfrunt]

You can't go by line length as the lines in yEnc are about twice as long as those with old uuEncoding. A 10MB file might have been 225,000 lines when posted in uuEncode, but comes out near 80,000 with yEnc. Factor in the line differences and it's the equivalent of 160,000 or so lines.

But yEnc in a nutshell for the people in this thread spreading half-truths:

Usenet was designed for text, not binary files. To transfer correctly, all binary files need to be encoded so the servers can handle them. The old method was uuEncode which sucked. Without going into the details, it bloated files by about 33%. So a 10MB file was actually 13MB when uploaded, stored on the server as 13MB, downloaded as 13MB and then decoded on your machine to become a 10MB file. This all happened tranparently, so most people didn't even know it was happening. Now we have yEnc which replaces uuEncode. It only bloats files by about 2%, so a 10MB file is uploaded as 10.02MB, stored as 10.02MB and downloaded as 10.02MB.

yEnc files are 30% quicker to upload, 30% faster to download and take 30% less room on the server, resulting in longer retention times. Do the math on a full movie post like a VCD. 2 discs, 600MB per disc. uuEncoded that 1.2GB becomes 1.6GB. yEnced it stays very close to 1.2GB, so the uploader saved hours of time and whoever is downloading it downloads 400MB less to get the same movie. It's a win/win situation. Just make sure you ignore the fools who mention yEnc and rar in the same breath. One is encoding, the other is compression and the two have nothing to do with each other. All Rars, mpgs, pictures, mp3s etc that are posted on usenet HAVE to be encoded with either uuEncode or yEnc. yEnc just works a lot better.

 

[LordMaul]

<< Amazing. I was just downloading Jedi Knight II >>




Fuskhead.


I will wait to buy it...




(Now...WHERE DID YOU GET IT?!??!!?! :Q)