Thanks.
It’s possible to have it entirely static and broker webrtc connections client-side, but I haven’t figured out a user experience that would make it “work”.
Thanks.
It’s possible to have it entirely static and broker webrtc connections client-side, but I haven’t figured out a user experience that would make it “work”.
P2P using peerjs (webrtc). Think of it like a gui for peerjs-server.
The docs for it can be seen here: https://positive-intentions.com/docs/projects/chat
I think it should have the links for more information.
The android app is poorly maintained I would stick to the website based version which I actively work on. I’m using tauri to wrap the webapp. I’m no java developer, that’s all tauri boilerplate.
Ultimately this is intended to be a general purpose messaging app. But it isn’t as good as any of the app you’ve suggested. I sharing it because it demonstrates a fairly unique browser based architecture. Aiming for secure client-side cryptography.
Unlike other solutions, as a webapp users can get started without installing or registering.
it certainly gives more control over your own data, but (if you know what youre doing) from a cybersec perspective, it can help to reduce the “attack surface”. the current direction is to allow users the flexibility from a version provided from me hosted on aws s3 or host it yourself from open source code. additionally, you can host your own peerjs-server as used for brokering connections… by default it connects to the public instance of peerjs-server (so its easier for users to get startedt).
im aiming for flexibility in “getting started” from ready-to-go to selfhosting. it all depends on if a user knows what theyre doing.
For testing and demo purposes only. NOT to replace any other app you use.
Session, Signal, Simplex and countless more apps are better for privacy and security. I can only hope to get to that level on my project.
Selhosting and a vpn are optional depending on your use case; the app works with niether to help users try it out and get started. Like all secure messaging apps, its better to selfhost given the option.
I’ve put effort into how the app is working, but ultimately i dont think its appropiate for me to suggest this code is ready for your sensitive data when it hasnt been reviewed or audited.
That’s unfortunate. Can you try clearing all site data and doing a page reload?
I’m trying to work on a better experience in a separate project here: https://p2p.positive-intentions.com/iframe.html?globals=&id=demo-p2p-messaging--p-2-p-messaging&viewMode=story