Code and Code Breaking

[Jamski]

I don't find anything humourous about nerve stapling lied Jamski through his teeth tying his dammdest not to giggle Just YOU try raising a nerve stapled child.

-Jam

[Vev]

What platform does people use? Because if I am really bothered, I could write a program to do code and decoding. The problem is which language to write it in. Most likely be either C or Java.

The current code I was thinking was using a simple network encoding, no encryption, using padded header, start bit, parity check, interleaved blocks, stop bits and padded trailer.

I seem to have missed some of the excitement, can someone tell me the status of the CyCon's code and whether it is crackable?

[Snowflake]

Originally posted by Vev
What platform does people use? Because if I am really bothered, I could write a program to do code and decoding. The problem is which language to write it in. Most likely be either C or Java.

The current code I was thinking was using a simple network encoding, no encryption, using padded header, start bit, parity check, interleaved blocks, stop bits and padded trailer.

I seem to have missed some of the excitement, can someone tell me the status of the CyCon's code and whether it is crackable?

Vev, the excel file I wrote the other day is really rough and could use a lot of work but if you could write a program in C or java that may be even better.

The CC has "invented" a new code system but it has not surpassed the area of "simple network encoding, no encryption, using padded header, start bit, parity check, interleaved blocks, stop bits and padded trailer". In fact it is far from there. In other words, it IS crackable. However I only worked on it for a few minutes so right now I was only able to decode one message and I still don't know what exact rule they are using.

[Snowflake]

Originally posted by Drogue
DBTS: 00101010011000110010101100001011100100110111000100 00001110100011010000110010100100000011001000110000 10110110101101110001000000110001101101111011001000 11001010010000000111010011011010110000101100100011 00010011000010110111000111010001000000011101001110 00000100000001000000101011101101000011000010111010 00010000001100100011010010110010000100000011110010 11011110111010100100000011101110111001001101001011 101000110010100111111

Learn the damn code! What did you write?

Looks like they are having trouble to read each other's message.

GooglieGod, Please don't let them know that their precious new code system is still crackable ... (pray ...)

[Nubclear]

Originally posted by HongHu
GooglieGod, Please don't let them know that their precious new code system is still crackable ... [/color] (pray ...)

He can't, because if he did....He'd lose all authority and neutrility.

[Snowflake]

Looks like the one I just decoded did not use any "new rules"

[Googlie]

Originally posted by HongHu
GooglieGod, Please don't let them know that their precious new code system is still crackable ...

'Course not. As Tass says, my neutrality would be jeapordized.

I can comment in a private forum on what is in the public domain, but even then, not if it divulges methods or infiltrations, etc

G.

[Snowflake]

Sorry to disappoint everybody but I just couldn't find their "new rule" at least for now. On a second thought, why did they use the earlier rule in the one that I decoded and say something like "learn the new code"? Do they want us to think that they really do have a new code and they really don't? Is it possible that they just write a bunch of garbage and wish we would be ferishly working to crash it? Hmmm...

Anyway I'm going to retire to my bed now. A wise man knows when to take a break. Let us watch the development and see if they do post a lot of these garbages "new codes". If it is that difficult to write that even their own people can't learn it, I doubt they'll be able to post a lot of such "codes".

GooglieGod, were you smiling? No I really want to know what you are doing right this moment, nodding? Shaking your head?

[Static Universe]

Originally posted by HongHu


Vev, the excel file I wrote the other day is really rough and could use a lot of work but if you could write a program in C or java that may be even better.

I've got the excel file but couldn't figure it out. Can you clarify?

[Gnool]

ŽØÞäò@èÞ@èÐÊ@ÒìÊB

Download my neato encoder/decoder, source included (You will need VB6 runtime libraries for it to work)

http://inthehut.org/og/GloryEncoder.zip

It's pretty simple, it takes the ascii code for the character and doubles it to encode it, halves it to decode it.

[Jamski]

NICE

They'll crack it eventually by working out the frequencys, so if we use this code, add lots of X's and Z's to bugger them up

-JAm

[Micha]

Originally posted by Micha
What about the "Huffman" Code?
It has a simple principle of encoding and decoding, but if you are not involved in that stuff, it is very confusing (since the letters have different numbers of bits, e for example has 1bit while Z has 6 bits).
If you like, I could create a formula using this. Just tell me

Since everybody here ignores what I say, I didn´t wait for your approval and wasted my whole weekend to develope an encoding system that is not so easy to crack, but still quite simple. It saves lots of space an time because, unless ASCII, it only uses the number of bits it really needs.

I counted out all the letters in two of our forum thread to find out which letters we use the most often and which not. So I created a Huffman-code regarding the probability of each letter. "e"s and "t"s now use less space than "x" or ":" symbols.

Do you agree to use that for coding our messages to the outer world? If so, I´d start to write a windows executable file for en-/decoding, or better: someone really knowing that stuff could write the program... I´ll deliver the key per e-mail or pm.

PLEASE DON´T IGNORE THAT POST AGAIN

[Static Universe]

Originally posted by Micha


Since everybody here ignores what I say, I didn´t wait for your approval and wasted my whole weekend to develope an encoding system that is not so easy to crack, but still quite simple. It saves lots of space an time because, unless ASCII, it only uses the number of bits it really needs.

I counted out all the letters in two of our forum thread to find out which letters we use the most often and which not. So I created a Huffman-code regarding the probability of each letter. "e"s and "t"s now use less space than "x" or ":" symbols.

Sounds good, can you give us a demonstration of how it will work?

PLEASE DON´T IGNORE THAT POST AGAIN

What post?!?

[Micha]

ok, a special preview for you

"The Hive is glorious" will be:
11010100011101000100011101101101111110011110001101 01011011010100010111011
That makes
9 eight-bit-rows to encode 20 symbols. That means an efficiency increase (in this case) of 110% compared to ASCII.

the trick is:
000="e"
110001110010="q"

That means the more often a letter occures in our common forum language, the shorter it is substituted. Plus, I added often used words like "Hive" as only ONE symbol (010001000). Statistically that is only 2.25 bits per letter (for the word "HIVE").

[Static Universe]

Do you have a decoder as well?