Macaroni Messenger 1.03

Date: 2026-06-14

Release type: documentation patch, officially nothing serious.

Main release idea:

Small documentation fixes.

What Changed

• Fixed documentation.
• Added one more document.
• Translated one more document.
• Added a link to the new document in Russian README.
• Added a link to the new document in English README.
• Added a link to the new document in the bilingual README.
• Made Russian docs aware that English docs exist nearby.
• Made English docs aware that the joke started in the Russian context.
• Clarified that Macaroni Messenger is an HTML file, not a server.
• Clarified that an HTML file does not store messages "on its side", because it has no side.
• Clarified that messages physically live in a git repository.
• Clarified that if the repository lives on a git host, the messages live with the git host.
• Clarified that this is a technical fact, not legal magic.
• Clarified that a normal messenger looks like messenger -> server -> database.
• Clarified that Macaroni Messenger looks like messenger.html -> git host -> git repository.
• Clarified the Russian context.
• Clarified that there are personal data operators, information dissemination organizers, electronic messages, and other words that make a lawyer appear in the room.
• Clarified that whether a specific regime applies depends on the specific service.
• Clarified that the document is not legal advice.
• Clarified that an HTML file is not a magic legal shield.
• Put GitVerse, GitLab, GitHub, Gitea, Forgejo, self-hosted GitLab, and corporate git hosting into one unpleasant architectural picture.
• Clarified that git hosting usually thinks it stores source code.
• Clarified that Macaroni Messenger politely adds conversations there.
• Clarified that .macaroni/chats/.../messages/.../*.json is an ordinary file for git.
• Clarified that for the user it is a chat.
• Clarified that for a lawyer it is the beginning of a beautiful workday.
• Added Sberbank, Yandex, and other adults to the room.
• Clarified that this is not hacking.
• Clarified that this is not bypassing anything.
• Clarified that this is not exploiting a vulnerability.
• Clarified that this is normal use of git hosting: create a file, read a file, commit a file, get history.
• Added two strategic chairs.
• Clarified the first chair: give users universal file storage, change history, API, tokens, public and private repositories.
• Clarified the second chair: close the API, cut CORS, break automation, and explain that it is for safety.
• Clarified that Macaroni Messenger does not choose the chair for the platform.
• Clarified that it only shows there are suddenly two chairs.
• Clarified that forking GitLab was not enough for a peaceful life.
• Clarified that an HTML file has no data center.
• Clarified that an HTML file has no rack.
• Clarified that an HTML file has no contract with electricians.
• Clarified that an HTML file has no night-shift DevOps team.
• Clarified that the hosting platform has all of that.
• Clarified that Macaroni Messenger does not prevent a host from complying with the law.
• Clarified that Macaroni Messenger does not encrypt the host transport against the host will.
• Clarified that Macaroni Messenger does not hide the fact that files are being written.
• Clarified that Macaroni Messenger does not break ACLs.
• Clarified that Macaroni Messenger does not pretend to be a system process.
• Clarified that Macaroni Messenger does not tell the user to "break the law".
• Clarified that Macaroni Messenger says: "here is HTML, here is git, here is JSON, it works".
• Added a "Completely Explicit" section.
• Clarified that Macaroni Messenger was not conceived as a tool for bypassing blocks.
• Clarified that Macaroni Messenger was not conceived as a way to break the law.
• Clarified that Macaroni Messenger was not conceived as a political manifesto.
• Clarified that the point is not the tool. The point is the users.
• Added an educational analogy about parks and raincoats.
• Clarified that before the Internet, exhibitionists went to parks.
• Clarified that this did not make parks or raincoats bad.
• Clarified that the author lives in Russia, votes, pays taxes, pays utility bills, and is not planning to move anywhere.
• Clarified that the joke is seriously, literally not fighting the law.
• Clarified that the joke is not bypassing blocks.
• Clarified the real question of the release:

okay, fine,
what if we store the whole conversation
and the keys publicly?
take it and read it, if you can

• Clarified that this is not a call to action.
• Clarified that this is an architectural experiment that understood "open infrastructure" too literally.
• Clarified that the pet project just happens to have tentacles, a pitchfork, and a tail sticking out of it.
• Clarified that this happened.
• Added the VPN, marketplace, and messenger story.
• Clarified that sometimes to open the marketplace, you need to turn the VPN off.
• Clarified that sometimes to open the messenger, you need to turn the VPN on.
• Clarified that between these two switches, the desire to sit in either one can disappear.
• Clarified that the freed time was used rationally.
• Clarified that we "wrote" this.
• Clarified that now you have to think about what to do with it.
• Clarified the final formula: if chat lives in git, the data storage question moves to whoever provides that git.
• Clarified that we are not calling anyone to do anything.
• Clarified that we are simply pointing at the APIs of adult platforms.
• Clarified that you know what to do.

The Almost Invisible Detail Near The End

Added documents:

• docs/legal-collision.md
• docs/legal-collision.en.md

This is a document about the legal collision that appears when a messenger has no backend, but messages live in git.

Short version:

if chat is stored as file history,
then it is stored by whoever stores file history

Everything else is small documentation fixes.

What Did Not Change

• Macaroni Protocol v1 did not change.
• .macaroni/ layout did not change.
• Encryption 1.01 did not change.
• GitHub/GitLab/GitVerse/Gitea/Forgejo adapters did not change.
• messenger.html is still one file.
• We still did not add a backend.

Result

Version 1.03 looks like a documentation release.

That is intentional.

Small documentation fixes.

Very small.