Privacy

10569 readers

596 users here now

A community for Lemmy users interested in privacy

Rules:

Be civil
No spam posting
Keep posts on-topic
No trolling

founded 3 years ago

MODERATORS

iopq@lemmy.world

Peer to Peer Messaging App (lemmy.nz)

submitted 2 months ago by GradleSurvivor@lemmy.ml to c/privacy@lemmy.world

30 comments fedilink hide all child comments

I have been working on an Android App quite a while now, starting from a simple idea.

A messenger where messages travel directly between phones with no servers in between. Using direct WebRTC encrypted connections (SRTP/DTLS), there are no servers that stores, reads, or relays content. Group chats use a gossip protocol where members relay to other members.

The only infrastructure the app touches is a signalling relay to set up the connection (no message content), a push notification to wake up a sleeping phone (also no content), and a TURN relay for restricted networks (encrypted packets only).

I wrote a detailed white paper explaining the full architecture: https://www.mindtheclub.com/white-paper.html

The app is in Open Testing on Google Play (1,000 tester cap): https://www.mindtheclub.com/beta-signup.html

I’m interested in this community's perspective on whether the architecture holds up.

you are viewing a single comment's thread
view the rest of the comments

[–] cypherpunks@lemmy.ml 1 points 2 months ago* (last edited 2 months ago)

you say this is “now documented” but you actually also mean now implemented, don’t you?

I just looked at github and i see that until this commit one hour ago (four hours after i asked) you were actually calling db.collection("users").document(peer.userId).get() to read a publicKey from Firebase

Yep, true

thank you for your (belated) honesty on this :)

So genuinely, thank you for your time and feedback, of course I respect the decision, not going to re-post

thank you and you're welcome