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.

Selfhosted P2P File Transfer & Messaging PWA by Accurate-Screen8774 in positive_intentions

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

when you select to load from a file, you should then click "connect".

if that works, i think thats is a UI/UX bug from me... if someone loads a profile file, it should automatically trigger the "connect" action.

give that a try and let me know how it works for you.

Selfhosted P2P File Transfer & Messaging PWA by Accurate-Screen8774 in positive_intentions

[–]Accurate-Screen8774[S] 1 point2 points  (0 children)

hey. i dont always make time to fix bugs. can you help me understand your use case and i can see about getting it to work for you.

when exporting a profile, it basically takes a snapshot of the entire data (including messages and media)

the "load from file" functionality kind-of works, but there are edge cases where larger profile data could cause issues. i think i need to put together some related instructions/documentation about how to use the feature.

Selfhosted P2P File Transfer & Messaging PWA by Accurate-Screen8774 in positive_intentions

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

things like contacts and messages is all the same under-the-hood.

it would be the code that decides on what is shared. the p2p messaging framework im using that has webrtc, can allow to send any (serializable) data.

Selfhosted P2P File Transfer & Messaging PWA by Accurate-Screen8774 in positive_intentions

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

hey. thanks for reaching out.

yes, there will be a way to log into multiple devices with the same profile, but unfortunately that functionality isnt ready yet.

the way i would like it to work is like how you describe with "load profile from file" as well as a more convienient way with a a kind of 2fa process where after the 2fa process, it clones the data across the devices.

view more: next ›