Collaborative Algo Design

My infinite compression algorithm seems to work but the
decompression results in garbage files, there are possible errors in source.
Since i don't want to waste more time(it get on my nerves to debug complex algos all day) with it(i have to work on my wiki engine and my game projects such as velox at astrum,sakura and vitae arcanum, which all are more fun to code, without all these soulless math tricks and bithacking).
Here is the source(its very alpha and it only does 1 level bitmap):
http://pastebin.com/FTuKvz1B
Note this is not the range compressor i discussed before,
it a single byte compressor i invented few days ago.
The old thread about it is at http://dis.4chan.org/read/prog/1318181159

Added to Infinite Compression subreddit with short explanation
http://www.reddit.com/r/InfiniteCompression/comments/l83ts/bytelevel_compressor_source/

>>1-2
You'll never be as annoying as the real FV.

>>3
I am the original. I just stopped using tripcodes and signatures. It detracts from the posts content and people start flaming the poster instead of discussing content.

In contrast to my range search compression, this one is not "Infinite" as in reducing the file to a hash-like value(s) for some function(s), it is transforming algorithm with small compression ratios(the ideas is that compression can be applied repeatedly, reducing size each time).
Test file for compression is:
http://marknelson.us/2006/06/20/million-digit-challenge/
http://marknelson.us/attachments/million-digit-challenge/AMillionRandomDigits.bin

>>3
No you aren't. We can tell.

>>6
No, he's cool like the original. I'm taking him for the original.

I love this thread so much

fuck off ``FrozenVoid''. Don't ever post again.

Hes the hero that /prog/ deserves, but not the one it needs right now...And so we'll hunt him...because he can take it...because he's not a hero...he's a silent guardian, a watchful protector...the Void Knight

There is no "real" FrozenVoid.  It's just a name, and anyone who posts using the name becomes everything it stands for.  It just happens to stand for retarded.

Another algorithm, with much better compression ratios: though decoding isn't working as planned. Its a XOR chain packed bitmap.
http://www.reddit.com/r/InfiniteCompression/comments/l8nql/xor_chain_sourcenot_working_yet/

I tried to compress Million Digits to a single byte using recursive merge& compress, result: after 6 iterations the size stays at 3 bytes(though files omit offset of start of bitmap and iterations,if with offset minimum size will be 4+1=5 bytes,+amount of iterations=6 bytes).  Still can't decode anything.

>>13
Still can't decode anything.
Lol'd at that part, don't know why.

>>9
Please try to ignore troll posts.
http://userscripts.org/scripts/show/40415

>>14
When one creates a compression algorithm in order to reduce storage requirements of archived data, we also expect to recover that compressed data at a later time.

ONE WORD: http://en.wikipedia.org/wiki/Lossless_data_compression#Limitations THREAD OVER