Calling it vibe coded slop without further details is just an insult. I’m clearly using AI, so let’s get that out of the way (welcome to 2026 software development). You immediately assume that I don’t know what I’m doing, so I typically don’t feel the need to answer… But you called for my humility so let’s proceed.
In the post I ask for you reach out for clarity on the details. But you don’t do that and that’s the basis of this “conversation”.
Let’s talk further about the approach with git. I started with a pure webrtc approach. A details I didn’t like about that approach is that you couldn’t send messages offline. I could create a more traditional database for messaging, I specifically wanted git because it allows for decentralised backups. While GitHub isn’t decentralised, the app allows for multiple remotes. Ideally for security, users would self host… The majority of users are not going to go for that option (even if they know how). so being able to use an existing service would make things easier for getting started.
When using git, I’m breaking all the rules. My use of git is explicitly not the traditional use-case.
- not using for version control
- I’m publishing encrypted sensitive messages - as per kerkhoffs principles
- I’m truncating history - so the storage doesn’t retain redundant details
- git with a combination of polling and syncing can be used to establish a webrtc connection without a dedicated backend. Something like this: https://github.com/positive-intentions/chat/issues/6
I’m up front about it on the docs that you won’t read. I’ve had feedback and questions as I’ve worked on this project. I’ve iterated and improved on the project while maintaining docs. I created loads of documentation for transparency. If your going to call that slop too, then I don’t want to pretend I’m having a conversation. The details around this project in the best best is still not going to be easy to read for most.
As always; feel free to reach out for clarity on any of the details.
a directed acyclic graph as a backend for a messaging app makes sense, it’s what matrix does.
In the older version of the project I was using a blockchain-like approach to help me keep ordering. But it’s was basically clunky and over engineered linked-list. It isn’t worth you time to look at but for reference:
https://github.com/positive-intentions/chat/blob/staging/src/components/blockchain/Blockchain.js
I used that approach because using git didn’t occur to me. Like you seem to have done, I associated git as only for version control of software, when it was a decentralised database. Git is also established well enough to offered multi-platform cross-compatability.
I was searching for an approach to a “decentralised database” and I didn’t want to use an actual blockchain (because yuck).