So it all started with an abstract thought. And I was on Developer tools and ChatGPT was on. A simple 5 character Hello is bloated onto multiple streaming calls converting that into 50 characters. And then I thought if we multiply this bloated ness because of the underlying transmitting medium is still JSON, can that JSON be compressed into a word of 36 character called Morse/36, basically FTIP which is From:To:Intent:Payload format. The origin was obviously morse the communication medium during world war. And then I looked around and I went deep in my memory when I saw an HL7 message embedded inside a JSON key over a REST call. Now, that is actually wrong at many levels. The message in itself is powerful. So all this is essentially some of the wrong implementations of REST because JSON essentially doesn't govern what can be the key or value against a key. Also, we were internally experimenting two different AI bots communicate with each other. So one is Alfred a CloudOps Engineer who is accessing Sophia which is a Voice AI Tutor infrastructure operations. So control panel which is me is communicating in a format which is very thin. Just FTIP. And that evolved into a standard "word" size of 36 and you just convey what you really want meaning the intent in 36 characters. Because Gradaually achieving compression is going wait on gradual implementations and by the time industry will wake up to the fact that even 1 character takes some space on some data center in some part of the world. Like if you compare with all these 6B param models the cost is huge. Even if we can bring down the cost by 1% measured when everything communicates in Morse-36, I think we saved a lot of Carbon footprint compared to what earths total server capacity = 1 ZB a zettabyte which one trillion gigabytes. But essentially think that much weight the earth can sustain currently through data centers. and while we can build more data centers - should you build data centers is counter question. So Morse/36 is an attempt. attempt to achieve a set compression level for content-on-wire compression. Initial thought process and commits are on the repository. https://github.com/TheGrahamFoun...

Forum Threads

p/morse-36-compact-machine-intent

•

1d ago

Opening a discussion thread centered around data compression in general

Like basically we want to establish a strict word boundary for a transmission between two entities. They can be a Frontend talking to a Backend or consuming a REST API. The mere fact that JSON has no native guardrails around the amount that can be sent, it is impossible to backport JSON for the cost is huge, so we go one step further in the realm of OSI model and picked a place. Presentation. Layer 6. Protocol. Morse/36.

View all

Morse/36 — Compact Machine Intent

A new age communications protocol

A new age communications protocol

Forum Threads

Opening a discussion thread centered around data compression in general

Forum Threads

Opening a discussion thread centered around data compression in general