snowflaxxx

Meet Teleport Pro

You're quoting me back at me. The quote is still correct. The backend doesn't exist. The messenger works. If that breaks your mental model of how software should be built — good. That was the point.

That’s literally what release 1.03 enables.

Fixed last night.

The GitHub-specific adapter is now one of several.

Not mine lol

That’s exactly what I thought after posting — so now it supports end‑to‑end encryption without a handshake. Still a single HTML file. Still no backend.

documentation was updated in the last few days. You might want to read the section about the funny legal collision this architecture creates — not sure, but it might apply to other jurisdictions too, not just Russia. Either way, it's an interesting side effect of using generic git hosting as a message transport.

My take: hitting three API endpoints doesn’t require a bundler or 400 MB of node_modules — most apps, especially hobby single‑page projects, can and should be built without a framework.

We don't say no backend — we say not our backend.

Email and SMS are faster. Also monitored, moderated, and mined.

Macaroni doesn't fix speed. It fixes who holds the keys — and who gets sued. That's the point.

Wellcome to the rabbit hole

You might find this branch interesting:

https://github.com/vanyapr/makaroshki/tree/macaroni

Turns out the messenger wasn’t enough, so now it also stores its own lore.

$2 for reading a text?

The closing </html> tag is mandatory because Macaroni Messenger plugins are inserted immediately before it. This is the convention defined by the plugin system.

That’s fair criticism of the current implementation.

The idea isn’t that transport magically disappears. The idea is that users don’t have to deploy, operate, pay for, or even think about transport.

GitHub happens to provide one out of the box, which makes the proof of concept extremely easy to try.

If I need to run databases, message brokers, servers and monitoring just to send my mom “please cook macaroni”, I’ve already lost interest.

True, but imagine this use case:

A messenger file with hardcoded settings and a hardcoded PGP key, stored on a USB stick.

You send a message.

Then you physically destroy the USB stick.

The client, the key, and the configuration are gone.

At some point the joke starts looking suspiciously like a dead-drop communication protocol.

How do you like that, FBI?

You just described the Macaroni plugin system — plugins are literally appended as <script> tags before the closing </html> tag.

That’s fair, although GitHub is just the default transport because it requires zero setup.

The protocol itself isn’t tied to GitHub and works with any Git remote.

If GitHub ever decided this wasn’t an acceptable use case, swapping the remote would be trivial.

The paradox is that Macaroni Messenger is absolutely a joke project.

But once you reduce everything to Git + JSON, adding things like PGP, age, signatures, encrypted attachments, or end-to-end encryption becomes surprisingly easy.

Which makes it even funnier.

At first glance it looks like a toy.

After a few minutes you start asking:

“Wait… why does this actually make sense?”

I think the protocol is a bit underestimated. People see the joke before they see the architecture.

There are some surprisingly interesting properties hiding behind the absurdity.

Maybe it’s a hidden gem.

Or maybe I’m just rationalizing a messenger implemented as a single HTML file.