Skinny/Fat Cons:
- They have lower entropy (less "random" data), they might be a text track.
Moreover, the pattern as described in the analysis, where first 7 bits of 3 tracks build a pattern that later fully appears in one of the tracks, has only 0,03% chance of happening at random.
To tell you the truth, I am confused with your argumentation. You are saying that the data from you analysis is
not random what proves that it is realy THE DATA, while at the same time you are saying that being
not random is a "cons" against blob track being THE DATA. It is confusing. I am leaning to thinking that if something I am seeing is
not random, it is an artifact resulting in how the authors "coded" the key. So any non-randomity I find, I try to exploit it searching for reasons it is there. I am actually happy to see any non-randomity in data as it gives me the way to look for WHY it is there.
I analysed the 6 bit "words" coming from the blob track (there are 25 of them, 6x25=150, + 2 bit outliers) and there are only 16 values. The chance for it is less than 0,5%. It MUST be a human creation, you see.
I ran a simulation in R, drawing 25-tuples from 64 pool with repeats, and out of a milion runs only 4544 had 16 or less unique values. So call it what you will, it is an anomaly to me - anomaly at worst, but human creation hopefully
If you carefully read what I wrote, then you'd see that I meant its not good for a random private-key bits in plain form. I did note its entropy is low, which points towards encoded text, so we agree on that. However, it can be also a case where the Author chose those at "random", and if you know some thing or two about magic
illusions, humans are not really good at RNG, so the data might be skewed and show repeated patterns.