How to Use BWTC32Key

This program has MANY uses, some of which are intended, and some of which were not originally intended, and I will go over how to use each of them:

Use 1: Secret files

Step 1: Set a password Step 2: Upload into the program, optionally setting compression level. Step 3: Copy the output text or download the .B3K file

To Decrypt: Step 1: Put the password in. Step 2: Upload the .B3K file or paste a string. Step 3: Download the decrypted file, setting file name and MIMEtype to what you desire

To send secret messages: 1: Either do the above with a text file, or put text in the encoder output box, and click the button that downloads a .B3K file, but change the nearby extension box to a .TXT 2: Upload the TXT into the program and encrypt as usual.

To Decode: Step 1: Decrypt the text file and either open it in a text editor, or upload it into the “Upload a B3K file” section, and click the button, and copy the text there, no need for Notepad. Keep in mind that all TXTs generated by BWTC32Key are UTF16BE, including Byte Order Mark.

You can use these strings to secretly convey messages, but keep in mind that if you see any characters that may be obscene in CJKV languages, I highly advise adding a space or other such thing to the key.

To compress but not encrypt: 1: Leave password box untouched or blanked (your choice). 2: Set a compression level if desired. 3: Download the .B3K as usual.

To decompress unencrypted files: Step 1: Leave password box untouched (or if that doesn’t work for the relevant file, blank it). Step 2: Download the decoded file.

To make a vocal synth: Step 1: Run a file through BWTC32Key as usual, generating a .B3K file, this should be about a megabyte. Step 2: Import into Audacity as raw data, selecting GSM as the encoding. Step 3: Isolate and cut out sounds from this, these give you vowels. Step 4: Run the .B3K file into Audacity as raw data in any other mode. Step 5: Really chop the resulting noise up, this will give you consonants. Step 6: Make a UTAUloid, which will require layering and stitching the above vowels and consonants, and then OTOing, etc.

To overdrive compression:

Step 1: Do the compression steps with the key of your choice, but type in a number of your choosing higher than 9 into the box (even decimals can work). Step 2: Download the .B3K file. Step 3: Run the file through the program as if you were decrypting it. Step 4: Download the decrypted file, and do a size check and a hash on it versus the original. Step 5: If something isn’t right, keep trying lower and/or integral sizes until it does it right. Yes, the files can be quite smaller, and yes, overdriving can and does work if done right.

To underdrive compression for extreme speed: Step 1: Compress with a level of one, or if you really want to go fast, a decimal number less than one. Step 2: Check the file as if you had just overdriven it, and redo with a higher decimal if needed.

To make color-bar flags: Step 1: Set a meaningful key, or one relevant to the flag you want. Step 2: Upload a blank or nearly-blank file. Yes, zero-byte files work, and yes, blanked keys work. Step 3: Download the .B3K file. Step 4: If the file input is a blank file, you should get a file that is 18 bytes long, other lengths may vary. Step 4a: Either way, open it in a hex editor. Step 5: Group the bytes together without spaces or 0x groups. Step 6: Split the resulting unseparated hex string into groups of three (short RGB), four (short RGBA) six (regular RGB) or 8 (RGBA) hex digits. Step 7: Make a flag out of these groups. If you do this with a blank file in regular RGB mode, you will end up with six RGB colors. The best way is Lunapic, though it prefers regular RGB. Set it to horizontal bars, or to make a statement and pay homage to the Androgyne flag or the PS3 and HD-DVD key flags, do vertical. Or you can do other patterns.

To make the most secure passwords: Step 1: Obtain a d120 from The Dice Lab. Step 2: Roll it several times, writing the rolls plus a comma and space on a paper. This is your physical recovery key. Step 3: Transcribe these numbers into a text file (I used Notepad on UTF16BE, but do what you want, any UTF transforms approximately equally). Step 4: Use the r/d120lists 120 Single-Word Personality Descriptions list as List 1, and the r/d120lists 120 NPC Professions list as List 2. Step 5: Roll for List 1 one (or multiple for extra paranoia) time(s). Step 6: Roll for List 2 one (or multiple for extra paranoia) time(s). Step 6a: One of each is double Diceware security. Step 7: Use the generated memorable two-word (if using only one roll from each list, helps with memory) password as a password for you to put in BWTC32Key’s password box. Step 8: Upload the file of d120 rolls. Step 9: If supported by the site, set the site password as the resulting string (Byte Order Mark may get stripped, so factor that in, though you can use the delete key on one on Windows). Step 9a: If the site doesn’t like your use of Unicode, convert the resulting string into UTF-7, save it as a text file, then open the resulting output as plain ASCII, and copy the Base64 string. Step 9b: If the site does not like the length: Truncate the password to the longest supported length. Step 9c: If the site does not like high length or Unicode: Do both 9a and 9b. Step 10: To log in: Put your memorable password into BWTC32Key. Step 11: Upload the rolls file. Step 11a: If you want to be paranoid, make a rolls file that when used with the memorable password logs you in, and one that’s a decoy to avoid people successfully logging in with the correct password if you are forced to give it. Step 12: Copy the resulting string. Step 12a: If you are paranoid enough to use an output string as a password for encrypting another rolls file (another is not required, just less-paranoid/secure), follow Step 10 with the prior output string as the “memorable” password, and proceed as normal. Feel free to use decoys and also do this type of recursion as many times as you think are necessary. Step 13: Paste the string (or the one you get from following the sub-steps of Step 9 when needed by garbage sites) into the password box of the site you want to login to.

To store Passwords: Step 1: Put that sticky note of passwords you have into a text document. Step 2: Use a memorable (d120-generated ones can work) password (or even a BWTC32Key-generated if paranoid, even recursive works) into BWTC32Key’s password box. Step 3: Upload the text file. Step 4: Download the .B3K file, and if you trust where you store text, store the BWTC32Key output string as text where you want.

To retrieve passwords: Step 1: Put in the password you set for the list. Step 2: Upload the .B3K file. Step 3: Decrypt the file and open it as text, and find the password you seek.

To use for WOFF3: Step 1: Use the program unencrypted on a TrueType file, or OTF. Step 2: Save the resulting .B3K file with a .woff3 file extension.

To decode: Step 1: Decode the file as if it were unencrypted. Step 2: Load the result as a TrueType/OpenType.

To use as a chunk format: Step 1: Run the bloated chunk data of your choosing into BWTC32Key, ideally unencrypted. Step 2: Make your format account for this.

To use for network packets: Step 1: Run data into the program set to encrypt input. Step 2: Make sure the intended other end knows how to decode it Step 3: Decode the packets.

To use for Bluetooth: Step 1: Run data into the program as you wish. Step 2: Send the resulting .B3K file over Bluetooth File Transfer on a paired device. Step 3: If the intended recipient and you know the key, after receiving the file, decrypted.

To make encrypted textual tarballs: Step 1: Use the program to encrypt a TAR file (obviously setting a password) Step 2: Download the file, adding a .tar extension prior to .B3K, and/or copy the text. Step 3: If the intended recipient, decrypt the file/string with the right password, download it, and then open the result as a TAR file, and untar it.

To make textual tarballs: Step 1: Follow the above, ignoring or blanking the password box.

To get rid of text spam: Step 1: Compress something that will give a resulting .B3K of around 4MiB, or larger. Step 2: If on a phone that splits up oversized messages and does not crash, send the entire string from the decoder box to the spammer.

To get rid of junk faxes: Step 1: Compress something that will give a resulting .B3K of 4MiB or larger for added fun. Step 2: Copy the text into a file, or just open the .B3K in a text editor. Step 3: Open the text document in Windows Fax and Scan or an equivalent, and use a font of your choice (UnifontEX perhaps). Step 4: Using a USB dial-up+fax modem (ideally use a fancy V.92+fax+voice modem) connected to your computer using said software, and send a fax to the source of junk faxes, making sure to include headers.

To make game ARGs/Easter eggs: Step 1: Run a file of your choice through BWTC32Key, as encrypted or unencrypted as you want. Step 2: Put the string into the game wherever you want that is reachable. Step 2a: If desired and applicable, put it as an unused string in the game’s Korean localization files to draw less attention, and use UTF16BE for it out of not making Hangul 3 bytes like UTF8 does). Step 2b: If desired, put a .B3K file in the game’s source tree and/or filesystem instead, helpful if dealing with large files. Step 3: Reveal the key wherever you please for fun and watch the fandom dig.

To hide stuff in code comments: Step 1: Encode something in BWTC32Key. Step 2: Put the string in the comments of your desired source code or webpage using a block comment tag.

To store binary blobs in source files: Step 1: Run your desired binary blob into BWTC32Key. Step 2: Put the resulting string into your source code.

To maximize e-mail throughput: Step 1: Use BWTC32Key on a file of your choice, encrypting it if desired. Step 2: Use the string as part of the message body, or a .B3K as an attachment.

To replace Face: and X-Face: headers: Step 1: Convert your favorite small image to BMP (or SVG). Step 2: Upload into BWTC32Key as unencrypted (or encrypted if you are secretive. Step 3: Put the string into your e-mail signature.

To replace Geek Code: Step 1: Generate a Combo Code string based on my specification and reference file. Step 2: Upload into BWTC32Key, ideally unencrypted, but if secretive you can encrypt it.

To make literary ARGs: Step 1: Make a PDF of your story (I use UnifontEX with LibreOffice). Step 1a: Put a BWTC32Key ARG into the body text if using most other formats. Step 2: Put the resulting string into PDF comments. Step 2a: For larger data, use something like PDFFeather if you lack Adobe Acrobat Pro to add a .B3K file as an attachment.

To encrypt Mastodon/Fediverse posts and/or attachments: Step 1: Follow the tutorial on secret messages. Step 1a: If encrypting attachments, send them as .B3K files.

To replace SCSU/BOCU-1 and add encryption: Step 1: Follow the instructions for sending secret messages.

To store data on microfilm: Step 1: Run BWTC32Key on file without encrypting it. Step 2: Print the resulting string on paper using Noto CJK Serif KR. Step 3: Ensure people know this, ideally translate that message into as many languages as possible, use UnifontEX for that “header”/cover page. Step 4: Put the resulting string and preliminary explanation onto microfilm using equipment that puts paper on microfilm. Step 5: Archive the paper if you have room, otherwise, dispose of it responsibly.

To replace PNG: Step 1: Save your image as a BMP. Step 2: Run through BWTC32Key.

To replace SVGZ: Step 1: See above, but use SVG, ideally without internal raster images, but if they exist, convert them to BMP. Step 2: Run through BWTC32Key.

To replace VGZ: Step 1: See above, but use uncompressed VGM files. Step 2: Run the VGM file into BWTC32Key.

To use for video game password saves: Step 1: Condense all the variables/states for your game into a save file. Step 2: Run through BWTC32Key.

To use for video game level codes: Step 1: Condense the level into a compact format. Step 2: Run through BWTC32Key.

To use for sending save files as text: Step 1: Run your save file through BWTC32Key.

To implement Pokemon-style events/Wonder Card-type DLC: Step 1: Put your event data into BWTC32Key. Step 1a: If emulating serial code events, post the serial code publicly before posting the data strings.

And that’s only the beginning! Can you find any new ways? I’ve found others but not all have exactly come into my mind at the moment in a step-by-step way.