EBG13

>Actually, if you can find TN #31 in the Technical Notes Stack 3.1, you will have had to run into an actual dogcow (Clarus) saying !fooM. Gee, wonder where that might be? Yours truly found it, and it was not that hard. I must say that the choice of encryption algorithm was extremely clever, however. You will never get it from the script unless you are fluent in ebg13, so you might as well try to solve it the right way!

1989 September 15, Earle R. Horton, “Moofing Dogcows!”, in comp.sys.mac (Usenet), retrieved 26 Jun 2022

Back in the old days, when people cared about decency on the Internet, it was decided that to keep people from seeing dirty words questionable material would be encoded in EBG-13. Nowadays it's just a technological quirk, however, unless by some freak of nature the CDA turns out to be constitutional, in which case we'll be seeing a lot more of SHPX and FUVG.

1997 March 11, David F Lynch, “alt.discordia and nightsweats”, in alt.sex.cthulhu (Usenet), retrieved 26 Jun 2022

[Warning: text ahead encoded in EBG13 to protect the innocent. No actual UI was emitted in the production of this mini-rant.]

2001 November 16, Garrett Wollman, “Forced into recovery”, in alt.sysadmin.recovery (Usenet), retrieved 26 Jun 2022

This is getting silly. Many monks can read EBG13 without pressing buttons, and EBGisms are part of the monastic culture [1].

2002 October 23, c...@nospam.netunix.com, “Proposed addition to FAQ.”, in alt.sysadmin.recovery (Usenet), retrieved 26 Jun 2022

>You yourself raised the encryption issue and certainly therefore know also that encryption keys used in firms etc. must be managed. That's the job of the IT people. The executives know nothing about it, and lack the skills to evaluate the strength of an encryption algorithm (heck, many of them can't decode EBG13, never mind something stronger).

2012 September 10, Moe Trin, “Measures against malware propagation”, in comp.security.firewalls (Usenet), retrieved 26 Jun 2022