u/bldrlife1

>!Hint: Source code to the program here!<

ciphertext : 3HpfwFPZn2hu3XWOuoprgzUDUbMdxuIQLVFOR

Hello, I wanted to share my program here because I thought it may be interesting to this field. My background is NOT computer science, however as a hobby I really enjoy tinkering with my machine and pushing the limits of what's possible.

About 8 or so years ago I became very interested in the subject of codebooks. My first prototype back then was made using a spreadsheet because that is all I could really understand as a rudimentary programming language. A few months ago I learned using today's tools it may be possible to rewrite the basic logic that goes into a codebook and set out to create my ideal code book. During the build process I attempted to follow Kerckhoffs's principle to a T.

The codebook is different from codebooks in the past (at least known codebooks) in a few ways.

1. The ability to rapidly generate unique 'keys' for distribution.
2. The size of the core dictionary...should be larger than any publicly available codebook
3. The dictionary is full of duplicates and large phrases which theoretically defeat the downsides of old codebooks, frequency analysis. You can encode the same exact message and the output will be different each time.
4. The ability to export long term key scheule. A full year key schedule comes in at about 5GB of raw data, BUT, if properly secured should ensure two parties can speak daily without ever being concerned.
5. Compose mode, which allows the user to ensure that their message will be encodable in realtime. It basically provides a window of context into the database as you type so that you can optimize the encoding for maximum compression.
6. What seems to be built in message integrity...here is what I mean by this. Because the total key space is 2,437,248!, IF the key does not match on the receiving end, the cipher text will decode to plaintext, but it will be complete nonsense. (see last image
7. Lastly, portability. This codebook is easy to distribute while old codebooks required a massive amount of resources to make and distribute. If the codebooks were compromised, there was no mechanism to rapidly re establish a new one. They were also big! This program will run on any computer including via termux.

The main difference between a codebook versus encryption, is codebooks operate on physical laws. a 14million digit key is not just hard, it's impossible to crack. Modern encryption operate on hardness assumptions that eventually can be cracked.

Here is the open source code and database if you want to tinker around! https://gitlab.com/here_forawhile/ed

Hello, made a app to assist in estimating materials for foundations. 100% offline and completely free. Find it here.

Maybe a lil crispy

Edit: tasted really good. It was a little past medium. I did about 6 minutes total I think I could turn the heat down a notch next time.

Not sure if this breaks the rules please remove if so. Made a completely free tool to estimate materials on the go and I am giving it away to hopefully help others. Nice for bid requests or material orders for smaller contractors. Find here.

I made this for myself to solve my own problems with punchlist management and am giving it away for free. If this breaks any rules please remove but I am not trying to sell or make any money here. It has genuinely made my job easier and just want to help others.

100% offline, no cloud, no bs, and zero subscriptions ever.

It's a way to quickly document and distribute punchlists to trade partners. You simply tap on the plans where there is an issue that needs addressed, take a picture, make a note, then export the pdf which shows the guy doing the work exactly where and what needs addressed.

There is also a lite suite of takeoff tools for when I need to measure and count stuff to order materials or generate bid requests.

No catch. I made this for myself and am just giving it away. 100% offline and no subscriptions ever.

Tutorial and links to Google play and appstore here

Basically, the database is full of all the tons of the most common phrases paired with a unique ID. On average it seems like I can compress my message to half the size. I wasn't really aiming to do this. I was just trying to make a code book and this was a byproduct and I thought It might be interesting to share.

But I got me thinking, what's the highest data compression we can get on text currently?

This is not a replacement for full desktop suites. It's designed as a tool for PM's/Supers out in the field who need to order materials, generate bid requests and scopes during the build process.

It is 100% offline and allows you to input your own company logo on the exported reports. I did spend quite a bit of time making this but I am giving it away for free for the love of the game!

TerminalPhone is a single, self-contained Bash script that provides anonymous, end-to-end encrypted voice and text communication between two or more parties over the Tor network. It operates as a walkie-talkie: you record a voice message, and it is compressed, encrypted, and transmitted to the remote party as a single unit. You can also send encrypted text messages during a call. No central server infrastructure, no accounts, no phone numbers. Your Tor hidden service .onion address is your identity.