I have developed AEC and tested it with PlugOS and an air gapped GPD MicroPC and it works nicely so far. Under PlugOS I used GL2AEC (Google Lens to AEC) to recover the AEC QR-Codes to been send.
I have added E2Q (Esub to QR-Code and Fetch to the repository.
Both programs can be used to send freely AEC ecrypted messages
to the Usenet Newsgroup alt.anonymous.messages, so that people
do not need an email address.
For that people can use the Nym Mixnet to Usenet Gateway at:
Great idea with a clean end-to-end implementation. The offline-encrypt, QR-transfer, online-deliver pipeline is well thought out.
One awkward part: the cold-start. Both parties need to pre-share public keys via the same air-gapped QR path, which means they basically have to be in the same room to bootstrap. Maybe a TOFU approach or a hybrid key directory (where only the fingerprint needs out-of-band verification) could make this much more practical.
Thanks. Well, regarding public key transfers. The GL2AEC program for PlugOS detects also public keys and not only AEC encrypted messages, so that Alice and Bob can do it the classic PGP way, while reading out loud the hex string via telephone, I would say. The only thing where they have to be in the same room, is when agreeing on a shared secret for the esub password, required for Usenet usage.
I also found out that the small thermal printer ZENWIRE TP-210 seems to work very well with AEC for postcards and letters, or possibly faxes. I’ll give it a try as soon as I get it.