Privacy

10569 readers

260 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

[–] dev_null@lemmy.ml 5 points 2 months ago (1 children)

Am I not seeing the actual white paper or is the "white paper" just a short blog post? Usually a white paper is a ~50 pages technical PDF, but you said detailed so I expected at least 100.

[–] GradleSurvivor@lemmy.ml -1 points 2 months ago

I agree, is actually quite high level, describing the main architecture and functionality`. What I intend to do, once the code is fully debugged, is to make my GitHub public, and upload a more detailed technical doc there. I thought not to make a public landing page, that targets a broader audience, too technical. In the meantime I'm happy to respond to any kind of technical question.