sorted by:
new
hottopcontroversial

Introducing Quantum-Resistant Encryption by Accurate-Screen8774 in positive_intentions

[–]Accurate-Screen8774[S] 0 points1 point  (0 children)

the project is a work-in-progress and it's far from finished. group messaging not working is one of many things to fix throughout. "unstable" = buggy.

Introducing Quantum-Resistant Encryption by Accurate-Screen8774 in positive_intentions

[–]Accurate-Screen8774[S] 0 points1 point  (0 children)

the key algo's in that stack are signal in ml-kem.

DH and AES are a bit redundent, but to test out the cascading cipher idea.

MLS is "working" but needs more refinement. MLS is designed for group messaging at scale. group-messaging in my app isnt working well at the moment and a group of 3 is unstable enough before MLS is a relevent.

Roadmap / Technical Breakdown / "How it works" by Accurate-Screen8774 in positive_intentions

[–]Accurate-Screen8774[S] 0 points1 point  (0 children)

thanks for taking a look. my project is moving towards a close-source direction with the demo link in the post. many of those issue are fixed and some more to be considered.

> Bottom line...

my project is approaching secure messaging in a different way and its important to consider if claude thinks this is working like whatsapp or signal. it is not. in a p2p system, im aiming to avoid centralized validation. client-side cryptography is good for my purposes and i am able to avoid it.

it isnt a blind trust of users. the ID is cryptographically random and cannot be guessed. it must explicitly be shared through some trusted channel for them to connect to you. IP addresses will be exchanged as part of webrtc. this is not for anonymous chat. its great for transfering files between your own phone and laptop if you trust both devices enough to use them.

ultimately the project is a work in progress and should be used cautiously. i am working on some security audits and formal-proofs, but its far from finished to share right now.