u/Accurate-Screen8774

https://preview.redd.it/85pjybp6wv0h1.png?width=910&format=png&auto=webp&s=2271ff55fee1eade7074506a02fe9e372a77f8a8

IMPORTANT: I am AI-slop-maxxing at scale... so lets get that out of the way. While this is aiming to be a more secure messaging app than Signal, Whatsapp, etc... it isnt audited or reviewed and so i DO NOT want you to "trust me". Its provided for testing and demo purposes only. This is a technical demo of a unique concept. Please use responsibly.

https://positive-intentions.com

This is intended to introduce a new paradigm in client-side managed secure cryptography. We can avoid registration of any sort. A fairly unique offering for a messaging app.

No need for things like phone numbers, email or registering to any app stores. There are no databases to hack. Allowing users to send E2EE messages; no cloud, no trace.

Features:

• PWA
• P2P
• End to end encryption
• Signal protocol
• Post-Quantum cryptography
• Multimedia
• File transfer
• Video calls
• No registration
• No installation
• No database
• TURN server

I started off with an open source version here: https://github.com/positive-intentions/chat

MVP Demo: https://chat.positive-intentions.com

The open source version is largely created manually (without AI agents). I am a software developer and creating webapps is my profession. I created it open source because it helps to be able to discuss details online. I think the core-concepts around client-side managed cryptography is demonstrated, but unfortunately open source isnt sustainable. So its unfortunate i have to consider introducing close-source components into the project, so that i can maintain a competative advantage.

Components now close source:

• UI component library: https://ui.positive-intentions.com
• P2P framework: https://p2p.positive-intentions.com
• Frontend: https://glitr.positive-intentions.com

I still keep some components open source for its importance in transparancy.

• Cryptography module - https://cryptography.positive-intentions.com
• Signal protocol - https://signal.positive-intentions.com

The close-source version of the app isnt finished enough to compare to existing tools like Simplex, Signal and WhatsApp. The goal is for it to be at least as secure as the Signal messaging app with their Signal protocol.

Take a look at some of the technical docs which ive updated to answer questions i frequently recieve in previous posts.

Technical breakdown and roadmap: https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown

The optimistic long-term goal (if its even possible), is to create the "worlds most secure messaging app". If you really want to see how to achieve that goal, you can take a look at the more comprehensive docs here: https://positive-intentions.com/docs/technical

Frequently asked questions: https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown/#frequently-asked-questions

i am AI-slop-maxxing... so lets get that out of the way. if you're looking for good code and best-practices, look away now. my demo here is far from finished and the UI is fairly clunky, but i hope its safe to share the slop i created in this sub.

https://ui.positive-intentions.com/iframe.html?globals=&args=&id=organisms-archivestudio--default&viewMode=story

unfortunately, it isnt open source, but i hope it helps to get feedback for improvements. in my project, the aim was to create an intuitive user experience for viewing zip files in a browser.

it is clearly absurd for something like this to be used by anyone on their own computer to view local zip files. the goal in my project is to enable the viewing of zip files in browsers after exchanging over webrtc.

Been Banned for AI-Slop on r/cryptography

The post that got me banned was basically a copy of this: https://www.reddit.com/r/cybersecurityai/comments/1sxvrmu/browserbased_file_encryption_no_install_or

i always provide a good amount of technical detail in my posts and i try to be as transparant and communicative about the details. These projects are very complicated and I try to document it well.

It's 2026 and all/most developers are using AI. I have used it to create things like formal proof and verification.

a separate but related project i was working on on is this. that is aimed to be a secure messaging app. i have all the bells-and-whistles there along with documentation.... but if the conversation cant move past "its AI-generated"... then it seems the cryptography community isnt aligned with the fact that using AI is now common practice for developers of all levels.

It's a bit reductive to call it slop. I think i try harder than most in providing links and documentation. Of course I used AI... and it's clearer for it.

i am of course sour from being banned there, but am i wrong to think my code isnt AI slop? some parts of my project are clearly lazy-ui... but im not sharing on some UI/UX/design subreddit. the cryptography module has unit tests and formal verification. if that is AI-slop and can result in me being banned, i simply dont have faith in that community to be objective on the reality of where AI can contribute.

while its understandable people dont want to review AI-slop... i think the cryptography community needs to get on board with the idea of using AI to help in reviewing such code. am i wrong? is the future of cryptography is still people performing manual review of the breathtaking volumes of AI code?

Hey. I was working on something that Id like to share. None of this project is audited or reviewed. and i want to confirm there will be breaking changes. So please please please DO NOT use this for any sensitive data!... but it would be great if you could share feedback on user experience and any features or functionality youd like me to include.

https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo

The UI there is pretty low-effort AI-generated, but in that version, there is a focus on how it's storing the data to be encrypted at rest. In the demo, a default password for AES is set (to help users get started in testing it out).

Browsers provide a filesystem API to allow webapps to access a folder on your drive. Its permission based, so user will have to explicily create and set a folder on their device.

When users try upload a file or image, the app will encrypt/decrypt on the fly. (e.g when uploading an image, it can be previewed in the app, but if you look at what is stored in your drive, you will see that the data is encrypted.)

the "how it works" is further described here:

https://positive-intentions.com/docs/research/Tutorials/dim/dim-file-storage

You can view the corresponding code here:

https://github.com/positive-intentions/dim

I am working towards a better UI (it's a UI demo only. No functionality):

https://ui.positive-intentions.com/iframe.html?globals=&args=&id=templates-filespage--default&viewMode=story&path=%2FDownloads

Passwordless encryption:

Id like to aim for a passwordless approach. Much more needs to be considered to address issues around ease of use and recovery if a key is lost.

https://www.reddit.com/r/CyberSecurityAdvice/comments/1ovw00q/thoughts_on_passwordless

IMPORTANT:

Nothing is safe to store in the app. There are countless bugs. The whole project is a work-in-progress. There will be breaking changes! This is for testing and demo purposes only. Not ready to replace any existing app... Im sharing to seek feedback on what features users would find useful.

Hey. I was working on something that I was vibecoding to the max! feel free to dive into the detials, but this project is pretty complicated and several details could be their own separate discussion.

None of this project is audited or reviewed. and i want to confirm there will be breaking changes. So please please please DO NOT use this for any sensitive data!... but it would be great if you could share feedback on user experience and any features or functionality youd like me to include.

https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo

The UI there is pretty low-effort AI-generated, but in that version, there is a focus on how it's storing the data to be encrypted at rest. the "how it works" is further described here:

https://positive-intentions.com/docs/research/Tutorials/dim/dim-file-storage

you can view the corresponding code here:

https://github.com/positive-intentions/dim

I am working towards a better UI (it's a UI demo only. No functionality):

https://ui.positive-intentions.com/iframe.html?globals=&args=&id=templates-filespage--default&viewMode=story&path=%2FDownloads