Anonymous ID: da1e65 Jan. 23, 2018, 8:34 p.m. No.143927   🗄️.is 🔗kun

>>143803

This is ridiculous. If the binary string is a key, all you really know about it is the number of bits. There are any number of different crypto algorithms that can take a key of a given length. You cannot infer what type of encryption was used just by examining a crypto key.

Anonymous ID: da1e65 Jan. 23, 2018, 8:59 p.m. No.144149   🗄️.is 🔗kun

>>144123

If it's meaningful he needs to explain it a whole lot better. What inputs is he using. What those inputs are looking up. How he generated the output list. Why he thinks it has significance. An example walking through his methodology to demonstrate what he's doing, at minimum.

Anonymous ID: da1e65 Jan. 23, 2018, 9:03 p.m. No.144192   🗄️.is 🔗kun   >>4220 >>4250

>>144127

No. This anon remembers. There was somebody trolling, trolling, trolling maybe 2 weeks ago. 3 days in a row, around this time of day, they kept posting images of a white cross supposedly found at the north pole on Google earth. Then, click the grayish area next to the white, and be "teleported" to some invisible island off the coast of West Africa. They posted this same images alongside all that. As well as some images supposedly of archeologists or something on that island doing some digging.

A mapfag came on and said it is a known glitch in Google Earth, not a "teleport" but simply a data glitch that always relocates your viewpoint to that specific place off the coast of West Africa.

A lot of anons wasted a lot of time on it.

Now this anon is posting the same identical image, and trying to assert that it is something "somebody" got from a Q image "a few breads ago".

I call B.S. If I'm wrong, prove me wrong.

Anonymous ID: da1e65 Jan. 23, 2018, 9:19 p.m. No.144345   🗄️.is 🔗kun   >>4413 >>4415

>>144256

Hmmm. That is not a clean hex dump. Some of the characters displayed are Unicode. A Unicode character is represented by multiple bytes.

 

For example BAĻ

that is not a capital L, it has some diacritical mark attached to the L. It is a Unicode character represented by multiple bytes.

A ways further in the string,

\84Ț\

That is not a capital T, it is a T with some diacritical mark attached (not the Roman alphabet). Therefore it is Unicode.

So your methodology for extracting hex data from this file is apparently going through some filter that is interpreting some of the hex data as multibyte characters.