1996-04-08 - Re: Spinners and compression functions

Header Data

From: JonWienke@aol.com
To: cypherpunks@toad.com
Message Hash: 0c0be97a1b11f33e1d8b3652fe24c62b5b6cc8e1ee490aca3377ea96efb80e1b
Message ID: <960408124222464915004@emout10.mail.aol.com>
Reply To: _N/A

UTC Datetime: 1996-04-08 22:06:24 UTC
Raw Date: Tue, 9 Apr 1996 06:06:24 +0800

Raw message

From: JonWienke@aol.com
Date: Tue, 9 Apr 1996 06:06:24 +0800
To: cypherpunks@toad.com
Subject: Re: Spinners and compression functions
Message-ID: <960408124222_464915004@emout10.mail.aol.com>
MIME-Version: 1.0
Content-Type: text/plain


In a message dated 96-04-08 04:01:28 EDT, stewarts@ix.netcom.com writes:

>Data contains varying quantities of predictablity and unpredictability.
>Some of the predictability has simple enough structure that a basic
>compression function can find and exploit it to squash the data.
>Some of the predictability doesn't.  For what it's worth, compressing
>the data before using it for other things does leave you with somewhat
>more consistent entropy per byte for "typical" random input, because it
>eliminates the easy stuff.

That was the entire point of my original posting on this subject.  I was
proposing using a compression function on spinner data, which contains very
little entropy and compresses well. (50 - 80% on idle loop timing data,
depending on processor load)  I don't believe I said anything about
compressing image data of any kind, or audio recordings of humpback whales
doing the wild thing, etc.  Noise sphere plots of ZIP files look pretty good,
regardless of how good or bad the plot of the unZIPed file looks.  (Raw idle
loop timing plots are terrible.)  I have posted a longer reply to Perry via
E-mail...

Jonathan Wienke





Thread