snowflaxxx

3 ms·

1.
by snowflaxxx 4mo ago
Meet Teleport Pro
2.
by snowflaxxx 4mo ago
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.
3.
by snowflaxxx 4mo ago
That’s literally what release 1.03 enables.
4.
by snowflaxxx 4mo ago
Fixed last night. The GitHub-specific adapter is now one of several.
5.
by snowflaxxx 4mo ago
Not mine lol
6.
by snowflaxxx 4mo ago
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.
7.
by snowflaxxx 4mo ago
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 a
8.
by snowflaxxx 4mo ago
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.
9.
by snowflaxxx 4mo ago
We don't say no backend — we say not our backend.
10.
by snowflaxxx 4mo ago
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.
11.
by snowflaxxx 4mo ago
Wellcome to the rabbit hole
12.
Macaroni Messenger 1.03 – small documentation fixes(github.com)
3 points by snowflaxxx 4mo ago|1 comments
13.
by snowflaxxx 4mo ago
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.
14.
by snowflaxxx 4mo ago
$2 for reading a text?
15.
by snowflaxxx 4mo ago
The closing </html> tag is mandatory because Macaroni Messenger plugins are inserted immediately before it. This is the convention defined by the plugin system.
16.
by snowflaxxx 4mo ago
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
17.
by snowflaxxx 4mo ago
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
18.
by snowflaxxx 4mo ago
You just described the Macaroni plugin system — plugins are literally appended as <script> tags before the closing </html> tag.
19.
by snowflaxxx 4mo ago
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 remot
20.
by snowflaxxx 4mo ago
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 mak
21.
Macaroni – a single HTML file messenger(github.com)
75 points by snowflaxxx 4mo ago|88 comments