This product was not featured by Product Hunt yet.
It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).

Product upvotes vs the next 3

Waiting for data. Loading

Product comments vs the next 3

Waiting for data. Loading

Product upvote speed vs the next 3

Waiting for data. Loading

Product upvotes and comments

Waiting for data. Loading

Product vs the next 3

Loading

Morse/36 — Compact Machine Intent

A new age communications protocol

Morse/36 Imagine getting a patient record from a remote hospitals network in just 36-characters. Imagine 2 fire drones talking with each other telling that they are out of gas and heading for refueling through a 36-character packet. Because while it is excellent, JSON is unnecessarily bloated. But we can not ask the industry to move away from JSON or prior to Morse/36 standards, but we are aiming to create a Presentation layer protocol ultimately. The sixth layer in OSI model.

Top comment

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...

About Morse/36 — Compact Machine Intent on Product Hunt

“A new age communications protocol”

Morse/36 — Compact Machine Intent was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #45 on the daily leaderboard. Morse/36 Imagine getting a patient record from a remote hospitals network in just 36-characters. Imagine 2 fire drones talking with each other telling that they are out of gas and heading for refueling through a 36-character packet. Because while it is excellent, JSON is unnecessarily bloated. But we can not ask the industry to move away from JSON or prior to Morse/36 standards, but we are aiming to create a Presentation layer protocol ultimately. The sixth layer in OSI model.

On the analytics side, Morse/36 — Compact Machine Intent competes within Drones, GitHub and Tech — topics that collectively have 697.7k followers on Product Hunt. The dashboard above tracks how Morse/36 — Compact Machine Intent performed against the three products that launched closest to it on the same day.

Who hunted Morse/36 — Compact Machine Intent?

Morse/36 — Compact Machine Intent was hunted by David Smith. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.

For a complete overview of Morse/36 — Compact Machine Intent including community comment highlights and product details, visit the product overview.