News:

Printed Amstrad Addict magazine announced, check it out here!

Main Menu
avatar_zhulien

Julian's Long List of Ideas Thread

Started by zhulien, 17:54, 12 February 25

Previous topic - Next topic

pelrun and 1 Guest are viewing this topic.

zhulien

claude and gemini flavours added
proxy added e.g. https://cyborgshell.com/proxy/?url=  (for gemini)

zhulien

ZOSCII is ready for commercial use!  https://cyborgunicorn.com.au/zoscii/zosciibb/

Anyone want to create a CPC Assembly Language encoder?

I will try soon if nobody better than me can...

CP/M source here in the src/c folder.  https://github.com/PrimalNinja/cyborgzoscii

and Linux/Windows zencode, zdecode, zstrength

Please report any bugs to me.

andycadley

So it's basically a one time pad (except you might re-use the pad, which leaves it open to histogram attacks).

And you have to use 16-bit character codes on an 8-bit machine because they will be faster than 8-bit ones?? And it doesn't really explain what the "character code" is supposed to be pointing at (bitmap data?)

zhulien

#78
Quote from: andycadley on Today at 11:16So it's basically a one time pad (except you might re-use the pad, which leaves it open to histogram attacks).

And you have to use 16-bit character codes on an 8-bit machine because they will be faster than 8-bit ones?? And it doesn't really explain what the "character code" is supposed to be pointing at (bitmap data?)
No, one time pads relate to encryption and there is no encryption here. Zoscii relates to ASCII as its a character encoding which is the intent. If you look at the source and the whitepaper you will see the performance gain on an 8bit system vs ASCII lookups. It is quite clear.

It increases performance of text output by not requiring offset calculations to a base ASCII table. It removes the need to waste ROM space with an ASCII lookup table. It does use 2x RAM (or ROM if messages are stored there) vs ASCII but RAM is reusable and ROM usually is not.

The side effect of this scheme is an unfalsifiable undeterministic plausible deniable security option with a practical infinite entropy (if you use a random file as the ROM file).

If you want to communicate with someone with an unknown shared ROM file you have 100% security with a good enough ROM file (check the JS encoder/verifier tool for ROM strength). No message is ever actually sent.  If you want to make your most important data inaccessible to anyone without the ROM file you can have 100% secured ability to do so with zero of your data in the address file. Don't lose your ROM though,  your data will be lost forever.

Powered by SMFPacks Menu Editor Mod