Replies (1)

• @xoron@infosec.exchange 2026-09-18 11:32

  @circus_maximus@social.anoxinon.de Think of git as like a backend. Individuals have their own git repos. Only you can write to your repo. Between peers the setup is basically public read access but only private write. Through a fairly slow process of polling and syncing repos you can read encrypted messages sent from peers and store them on your own with read-reciepts. Maybe this helps to illustrate the approach: https://programming.dev/post/56710507 The process of polling and syncing is horribly slow, but under-the-hood, it tries to establish a webrtc approach. That can be achieved without a backend like described here: https://github.com/positive-intentions/chat/issues/6 When connected over webrtc, you can exchange messages through that separate channel and avoid having to sync git repos. Right now it's still a work in progress. Git is storing all the app data. (Encrypted where appropriate). I will be working towards reducing that storage so messages on client-side only. The client-side storage approach is better demonstrated in the Enkrypted Chat project: https://positive-intentions.com/blog/introducing-enkrypted-chat That Enkrypted Chat project seems more mature than this project but the project in this post is the superior approach. It will soon reach a match in capabilities (and beyond).

  Open ##5219554