pull down to refresh

Innocuous is lilting around in a "calm before the storm". Basically need some test infrastructure code before one last big refactor which will add headers to encoded/decoded data which include a length, nonce, and version along with the actual data.
Been talking to a lot of people IRL about the project but not many seem interested or can think of use-cases. I did talk to one lady this week at in at ETH conference that had written papers on this underlying subject called "steganography". On a walk I realized one of the primary use cases is procedurally generated NFTs.
I've also been able to develop an easy way ti explain the concept in markdown which I'll paste below.
Thanks for doing these @deSign_r!
Ups and downs, soups need to settle after cooking to test much better. Even these small steps helps refine and improve the idea. Especially talking with people irl and if at some stage you have a demo to put users in front of it and try to solve a specific need or use case, then is when you'll start getting real value/feedback that will help bring the product forward and exponential steps.
This table go above my head, look's like some encryption and encoding knowlede is needed to read it. It will be a great demo for those that can read it. Well done!
reply
The following example encodes the ascii char "h" (or the bits "01101000") with a chunk_size=2.
Iter 1Iter 2Iter 3Iter 4Iter 5Iter 6
Selection (token)TheAquariumisaworld
Selection (encoding)0110n/an/a1000
Cumulative encoding0101100110011001101001101000
Index (encoding 2-bit)encodedencodedacceptedacceptedencodedencoded
0 (00)" It": 0.2958" aqu": 0.4469"arium": 0.9999" is": 0.8619" located": 0.4782" world": 0.1646
1 (01)" The": 0.26917" New": 0.4136"ari": < 1e-4" has": 0.0591" home": 0.2787" global": 0.1238
2 (10)" This": 0.1813" Aqu": 0.1020"aram": < 1e-4" features": 0.0182" a": 0.0926" must": 0.0958
3 (11)" Loc": 0.0318" Boston": 0.006"a": < 1e-4" offers": 0.0164" one": 0.0540" non": 0.0876
reply