... if you're geeky enough ... |
Pretty cool. Why don't you publish the scripts?
Pretty cool. Why don't you publish the scripts? |
44 65 61 72 20 4d 72 20 43 79 72 6f 3a 20 49 20 61 70 70 72 65 63 69 61 74 65 20 74 68 65 20 61 6e 6e 6f 79 61 6e 63 65 20 63 61 75 73 65 64 20 62 79 20 74 68 69 73 20 6c 69 74 74 6c 65 20 73 6f 63 69 61 6c 20 65 78 70 65 72 69 6d 65 6e 74 2c 20 61 6e 64 20 69 74 20 77 69 6c 6c 20 62 65 20 6f 76 65 72 20 69 6e 20 61 20 66 65 77 20 6d 6f 72 65 20 64 61 79 73 2e 20 20 49 20 77 69 6c 6c 20 6e 6f 74 20 22 73 68 75 74 20 74 68 65 20 66 75 63 6b 20 75 70 22 2c 20 62 75 74 20 79 6f 75 27 72 65 20 66 72 65 65 20 74 6f 20 69 67 6e 6f 72 65 20 6d 65 20 69 66 20 79 6f 75 20 6c 69 6b 65 2e 20 20 50 65 61 63 65 2e |
In case no one told you, allow me to be the first: It looks like shit. |
Okay, who do I thank with what for Libman ceasing the posting of potentially disturbing material?
Me and you know what.
When you right-click your desktop (assuming you're using Windows), select Properties, and open the Settings tab in the "Display Properties" window, what does it say under color quality? It looked fine to me under both 16 and 32 bit.
Or did I? The world may never know... 8)
However, if you're geeky enough, you might be able to figure this out (http://en.wikipedia.org/wiki/Steganography). Notice how my recent posts all look weird? Well, if you look at the source code (i.e. click "QUOTE"), you will notice a lot of extra formatting tags. Their visual effect is very subtle, but they are there for a reason. There is a bitstream (http://en.wikipedia.org/wiki/Bitstream) hiding in them! You'll notice that some tags (only those which are auto-generated by my script) contain random casing: that's one place where the bits are hidden. Another place is the font color codes (http://en.wikipedia.org/wiki/Web_colors): notice that there are up to four color categories (normal, vowels, numbers, and punctuation): some may be turned off automatically to fit the data into the 20,000 character per-post limit. Each of them starts with a particular color, but sometimes this color shifts subtly: that's another place the bits are hidden.
Messages that contain fewer than 32 bits are useless, because that's the header identifying where those bits belong (i.e. position in a file). The rest of the bits are the data. (Notice that if I'm quoting a message from someone else, which could include a message quoted from me, it could include tags that look to contain the bitstream but could contain garbage that throws off your decoder script.) If the bitstream reaches the end of file, there will be an EOF (end-of-file) control character (8 bits), followed by another 32-bit address like in the beginning, followed by another bitstream.
I've already put through one small JPEG file, and ran a script to piece it together again. More than once, actually, because indicating the file position in every message makes harmless repetition possible, which also works as a redundancy check and it makes no difference in which order the bitstream chunks are processed.
So, um, enjoy. :lol: