GitHub as Cloud Storage

GitHub as Cloud Storage

Im sure im not the first consider this approach, but i would like to share a demo for clarity and transparancy. No need to debug, its far from finished and there is much to do.

Im working on a P2P messaging app and generally up until recently i thought in such a system, if a peer is offline, you cant send a message... It wouldnt be "decentralized" if there was some central queue of messages.

It took embarassingly long, but then it hit me... git... just regular git is a decentralized database. Github isnt decentralized, but git can have multiple remotes that can act as redundencies.

In my setup i need the ability for others to be abe to read and only i should be able to write to it. That functionality is out-of-the-box in git.

Git is also pretty standardized so there are many providers if users want to move away from Github.

The storage requirements for my project are fairly small. Typically small text messages. The data itself thats publicly readable would be encrypted (aiming to keep aligned to Kerkhoffs principles).

There is much more to improve and consider there for things like encrypting the data at rest.

I have concerns around if providers like GitHub, Codeberg and Gitlab might see the way my app works as fundamentally violating their terms-of-service.

IMPORTANT DISCLAIMER: This is open source for transparency, testing and demo purposes only. it is still a work in progress and far from finished. you should not use it on any sensitive repositories. There WILL BE breaking changes. Use responsibly.

u/Accurate-Screen8774 — 2 days ago
▲ 4 r/learnrust+2 crossposts

New to Dioxus and Rust. Any tips about getting started?

Hey, I'm a webdev. I previously approached my project with JavaScript. I'm familiar with the js ecosystem.

I put a fair bit of consideration and in contrast to my JavaScript-approach, I'd like to investigate Dioxus.

I'm not completely new. I've dabbled in Rust before. I have read a lot of the docs and I'm sure there is much more to learn and practice.

What advice would you give to getting started with the Rust ecosystem approach?

Similar to a lot of languages there are considerations for things like tests. So it would be helpful to compare the options. As well as any other best-practices and nuances.

In relation to my project, I'm particularly interested in the tooling available in Rust for formal verification.


Just to be clear, im not here to waste your time on my slop, but if you want to see what I've got so far (practically nothing):

u/Accurate-Screen8774 — 4 days ago
▲ 2 r/ask_privacy+1 crossposts

How do i get academic scrutiny on my project?

im a software developer and so far when promoting my project on reddit, it is "not well recieved" because im framing it as a product. people hate being advertised to.

the reponse is completely understandable, but that framing seemed nessesary in order to encourage people to take a look. if i hint at it being "research and development", people simply wont take a look. completely understandable given that cryptography isnt particularly inviting from the onset.

reddit is not the place for feedback on a project like mine. the space for "cybersecurity" is understandably competative. i think my project demonstrates a unique approach, but its clearly not a reason to waste someones time if the documentation isnt clear enough.

... so where/how should i share my project for it to be scritinised. i certainly dont want to waste anyones time so id like to also ask what details would be important to share.

ultimately it could just be that my project is bad and i should feel bad. perhaps i need a reality-check that the system is designed to keep bums like me out.

ive heard of things like arxiv, but that seems it might demand a higher calibre of documentation and so id like more advice there so if i post, it isnt flagged as trolling.

i have loads of documentation on my project, i suspect i just havent figured out the correct way to assemble it so that its comprehensive.

i appriciate any tips/adive you can offer.

reddit.com
u/Accurate-Screen8774 — 21 days ago

VibeCoding and CyberSecurity shouldnt work this well

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

Decentralized browser-based P2P E2EE messaging.

The key detail that sets this apart from other messaging apps is the browser-based client-side cryptography philosophy.

No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

This app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, it's impossible to claim any system is the "world's most secure". It ultimately depends on your threat model. By reducing the architecture's attack surface, the aim is to consolidate complexity to client-side.

... but wait. Im only getting started. That version works as an MVP, but i see the flaws of my approach and am going to do it better. Im going to proceed on the project and create "version-2".

I hope the latest version of project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout... This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. I listened to feedback and proceeded. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

IMPORTANT: While this is aiming to provide a secure experience, It is not audited or reviewedShared for testing, feedback and demo purposes only. Please use responsibly.

reddit.com
u/Accurate-Screen8774 — 22 days ago
▲ 2 r/PWA

Browser-Based Signal Messenger Alternative

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

The key detail that sets this apart from all other apps is the browser based client-side philosophy.

No need to install anything. Your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. Your ID is unguessable and to connect to someone, you have to explicitly share it.

WebRTC has other nuances like being to route through a shared network for secure/faster transfer.

This app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, it's impossible to claim any system is the "world's most secure". It ultimately depends on your threat model. By reducing the architecture's attack surface, the aim is to consolidate complexity to client-side.

... but wait. Im only getting started. That version works as an MVP, but i see the flaws of my approach and am going to do it better. Im going to proceed on the project and create "version-2".

I hope the latest version of project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout... This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possibl

This is intended to demonstrate client-side managed secure cryptography.

I know ive tried to compress a lot of my journey into one post. The project above is going to be tricky to understand. Feel free to reach out for clarity on any of the details.

IMPORTANT: While this is aiming to provide a secure experience, it cannot be audited or reviewed. Shared for testing, feedback and demo purposes only. Please use responsibly.

reddit.com
u/Accurate-Screen8774 — 22 days ago

I'm working on a cybersecurity-related project

The main pushback I get it that I'm using AI.

In practice, I'm doing things like creating unit tests and documenting things like formal verification. I don't need AI to do this work. It's only my time I'm wasting to write every line. It's all quite some effort.

I'm fairly proud of my work. Various details are open source. It's understandably too complicated for anyone in their spare time, but it's an option.

Are others facing similar "merit-less" pushback?

reddit.com
u/Accurate-Screen8774 — 23 days ago

Signal Messenger Clone

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

The key detail that sets this apart is the browser based approach.

No need to install anything. your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. your ID is unguessable and to connect to someone, you have to explicitly share it.

webrtc has other nuances like being to route through a shared network for secure/faster transfer.

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

I know the project above is going to be tricky to understand. It might help to understand with an open-source version of the concept, but have since deprecated it in favour of the version linked above.

https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

Feel free to reach out for clarity on any details.

reddit.com
u/Accurate-Screen8774 — 23 days ago

Signal Messenger Clone

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

Im trying to innovate in the age-of-AI. So i often find myself defending the project from being called AI slop. i have been working on imrovements throughout the code as well as the docs.

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

I know the project above is going to be tricky to understand. It might help to understand with an open-source version of the concept for educational purposes. Its's important to note, i have since deprecated it in favour of the version linked above.

Open source demo (deprecated)

PS. Im calling it a "Signal Messenger Clone"... that just a matter of how to frame it for users. It doesnt work in a way thats comparable to the signal architecture. This project is fairly complicated and the links above are likely not going to be enough, so feel free to reach out for clarity on the details.

reddit.com
u/Accurate-Screen8774 — 23 days ago

European-Based Signal Messenger Alternative

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

The key detail that sets this apart is the browser based approach.

No need to install anything. your ID is crypto-random and so the app doesnt need to rely on any central registration system like phone numbers. your ID is unguessable and to connect to someone, you have to explicitly share it.

Webrtc has other nuances like being to route through a shared network for secure/faster transfer.

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

I know the project above is going to be tricky to understand. It might help to understand with an open-source version of the concept, but have since deprecated it in favour of the version linked above.

https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

reddit.com
u/Accurate-Screen8774 — 24 days ago

Privacy-First Signal Messenger Clone

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll never be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

p.s. I know people love open-source and the project above is going to be tricky to understand. it might help to understand with an open-source version of the concept, but have since deprecated it in favour of the version linked above.

https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

reddit.com
u/Accurate-Screen8774 — 24 days ago

Privacy-First Signal Messenger Clone

https://preview.redd.it/o1nad3btktfh1.jpg?width=1080&format=pjpg&auto=webp&s=7d7617dd0e12cb8032c737b723af6126ecf31bb9

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll ever be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

PS. I know the project above is going to be tricky to understand. It might help to understand with the following open-source version of the concept (the MVP to the version linked above).

https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

reddit.com
u/Accurate-Screen8774 — 24 days ago

Privacy-First Signal Messenger Clone

https://preview.redd.it/la2cyrz81tfh1.jpg?width=1080&format=pjpg&auto=webp&s=7a093c55f09b6302ae900cbbb8a0f14af6016fd0

I hope this project has reached a level i can share the following details. I've made a genuine effort towards documentation and transparancy. I dont think it'll never be enough and so im still concerned it isnt ready to share. While im using AI throughout. This is not a vibecoded project. There is attention throughout for unit tests and formal-verification. With your feedback, id like to make improvements for clarity throughout.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. I know it's impossible for any system to be the "world's most secure", but that isnt a reason to not try. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

p.s. I know people love open-source and the project above is going to be tricky to understand. it might help to understand with an open-source version of the concept, but have since deprecated it in favour of the version linked above.

https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

reddit.com
u/Accurate-Screen8774 — 24 days ago

Privacy-First Decentralized P2P Messaging With The Signal Protocol

https://preview.redd.it/ccwcfk6ojsfh1.png?width=1420&format=png&auto=webp&s=d7df716b370b05b997c5ad15b65fd94d45261372

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, I know it's impossible for any system to be the "world's most secure". By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

reddit.com
u/Accurate-Screen8774 — 24 days ago

WhatsApp Clone

The goal is to create the most secure P2P messaging app.

This app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, it's impossible to claim any system is the "world's most secure". It ultimately depends on your threat model. By reducing the architecture's attack surface, the aim is to consolidate complexity to client-side.

Features:

  • Webapp
  • Peer to peer
  • Local-only
  • No installation
  • No registration
  • End to end encryption
  • Multimedia
  • File transfer
  • Video calls

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing. Feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

  • JavaScript and cybersecurity?
    • By aiming to have it run client-side (including statics) we can eliminate concerns around malicious payloads from the network provider. See best practices here and guides on selfhosting here.
  • EU Chat control?
    • Chat control doesn't seem like it would affect this app. Open to feedback here.
  • Production-ready?
    • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready. The production version is also a work-in-progress, but can be seen here. Find out more here.
  • Paywall?
    • Its completly free, open-source, selfhostable and unlimited to use.
  • Vibecoded?
    • This version is not vibecoded. The git repo and docs are linked for transparency. Feel free to reach out for clarity.
reddit.com
u/Accurate-Screen8774 — 25 days ago

Browser-Based P2P Messaging App

This is a technical demo of a fairly unique approach using a browser-based, local-first and webrtc approach.

This is intended to demonstrate client-side managed secure cryptography.

Features:

  • Core
    • PWA
    • P2P
    • Local-first / Local-only
    • No installation
    • TURN server
    • Encrypted-at-rest
  • WhatsApp clone
    • End to end encryption
    • Signal protocol
    • Post-Quantum cryptography
    • Multimedia
    • File transfer
    • Video calls
  • Nextcloud clone
    • Word
    • Spreadsheet
    • PDF
    • file-transfer
    • Encrypted vault

Some open source versions of the core concepts.

Feel free to reach out for clarity instead of diving into the docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited or reviewed. Shared for testing, feedback and demo purposes only. Please use responsibly.

reddit.com
u/Accurate-Screen8774 — 25 days ago
▲ 1 r/foss

WhatsApp Clone

The goal is to create the most secure P2P messaging app.

This app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, it's impossible to claim any system is the "world's most secure". It ultimately depends on your threat model. By reducing the architecture's attack surface, the aim is to consolidate complexity to client-side.

Features:

  • Webapp
  • Peer to peer
  • Local-only
  • No installation
  • No registration
  • End to end encryption
  • Multimedia
  • File transfer
  • Video calls

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing. Feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

  • JavaScript and cybersecurity?
    • By aiming to have it run client-side (including statics) we can eliminate concerns around malicious payloads from the network provider. See best practices here and guides on selfhosting here.
  • EU Chat control?
    • Chat control doesn't seem like it would affect this app. Open to feedback here.
  • Production-ready?
    • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready. The production version is also a work-in-progress, but can be seen here. Find out more here.
  • Paywall?
    • Its completly free, open-source, selfhostable and unlimited to use.
  • Vibecoded?
    • This version is not vibecoded. The git repo and docs are linked for transparency. Feel free to reach out for clarity.
reddit.com
u/Accurate-Screen8774 — 25 days ago
▲ 0 r/eutech

Chat Control vs Decentralized Chat

I'm trying to create the "most secure messaging app ever"... Not just "more secure" than something like Signal or WhatsApp... a different approach fundamentally.

Signal doesn't create a webapp for legitimate reasons around how that project is architected. I hope in this approach I can overcome those limitations.

This is the deprecated open source MVP: https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

The new version of the app demonstrates a more polished approach to using a browser-based, local-only and webrtc approach. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible to the "theoretical" concept of the "most secure messaging app ever".

This is intended to demonstrate client-side managed secure cryptography.

Features:

  • Core
    • PWA
    • P2P
    • Local-first / Local-only
    • No installation
    • TURN server
    • Encrypted-at-rest
  • WhatsApp clone
    • End to end encryption
    • Signal protocol
    • PQ cryptography
    • Multimedia
    • File transfer
    • Video calls
  • Nextcloud clone
    • file-transfer
    • Encrypted vault
    • folder sync
  • EuroOffice clone
    • Word
    • Spreadsheet
    • PDF
    • Code

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing, so feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

  • Audit?
  • EU Chat control?
  • Production-ready?
    • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready.
  • Paywall?
    • Its completly free and unlimited to use. The free and paid plans on clerk are currently the same experience.
  • Version 3?
    • "Enkrypted Chat" is the latest public version. It hold the designation of "version 2". I am actively investigating options for "versions 3" which would then be a further improvement on the approach. "Version 3" is still at the concept stage and not ready to demo.
reddit.com
u/Accurate-Screen8774 — 25 days ago

The Most Secure Messaging App Ever - Prove Me Wrong

I'm trying to create the "most secure messaging app ever"... Not just "more secure" than something like Signal or WhatsApp... a different approach fundamentally.

Signal doesn't create a webapp for legitimate reasons around how that project is architected. I hope in this approach I can overcome those limitations.

This is the deprecated open source MVP: https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat

I was suprised to learn that open-source is surprisingly worthless. if i cant get funding for the project at that level of open-source transparency... I've lost faith in expecting open-source support. It only stands to put me at a competative disadvantage. I leave it open source because i want to contrast it against my next version, the project is going to be magnitudinally more sophisticated. Perhaps naive, but i dont think there is any way someone is going to take my open source project and create something competative against what im planning for with version-2... the new production-grade build.

The new version of the app demonstrates a more polished approach to using a browser-based, local-only and webrtc approach. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible to the "theoretical" concept of the "most secure messaging app ever".

This is intended to demonstrate client-side managed secure cryptography.

Features:

  • Core
    • PWA
    • P2P
    • Local-first / Local-only
    • No installation
    • TURN server
    • Encrypted-at-rest
  • WhatsApp clone
    • End to end encryption
    • Signal protocol
    • PQ cryptography
    • Multimedia
    • File transfer
    • Video calls
  • Nextcloud clone
    • file-transfer
    • Encrypted vault
    • folder sync
  • EuroOffice clone
    • Word
    • Spreadsheet
    • PDF
    • Code

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing, so feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

  • Audit?
  • EU Chat control?
  • Production-ready?
    • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready.
  • Paywall?
    • Its completly free and unlimited to use. The free and paid plans on clerk are currently the same experience.
  • Version 3?
    • "Enkrypted Chat" is the latest public version. It hold the designation of "version 2". I am actively investigating options for "versions 3" which would then be a further improvement on the approach. "Version 3" is still at the concept stage and not ready to demo.
reddit.com
u/Accurate-Screen8774 — 25 days ago

I'm trying to create the "most secure messaging app ever"

I'm trying to create the "most secure messaging app ever"... Not just more secure than something like Signal or WhatsApp, but a different approach fundamentally.

https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat/

Signal doesn't create a webapp for legitimate reasons around how that project is architected. I hope in this approach I can overcome those limitations.

I can't get traction on the open source approach so I'm moving towards a close-source approach as I make improvements throughout to create something competitive and production-grade (I might open source it at a later date).

This new version of the app demonstrates a more polished approach to using a browser-based, local-only and webrtc approach. By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible to the "theoretical" concept of the "most secure messaging app ever"

This is intended to demonstrate client-side managed secure cryptography.

Features:

  • Core
    • PWA
    • P2P
    • Local-first / Local-only
    • No installation
    • TURN server
    • Encrypted-at-rest
  • WhatsApp clone
    • End to end encryption
    • Signal protocol
    • PQ cryptography
    • Multimedia
    • File transfer
    • Video calls
  • Nextcloud clone
    • file-transfer
    • Encrypted vault
    • folder sync
  • EuroOffice clone
    • Word
    • Spreadsheet
    • PDF
    • Code

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing, so feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

  • Audit?
  • EU Chat control?
  • Production-ready?
    • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready.
  • Paywall?
    • Its completly free and unlimited to use. The free and paid plans on clerk are currently the same experience.
reddit.com
u/Accurate-Screen8774 — 26 days ago
▲ 7 r/CorpFree+1 crossposts

Decentralized P2P Chat Part 2

Following my previous post about secure p2p browser-based messaging, I further built on the idea to better illustrate that I'm trying to create the "most secure messaging app ever"... Not just more secure than something like Signal or WhatsApp.

Part 1: https://www.reddit.com/r/CorpFree/comments/1uytump/decentralized_p2p_chat/

I'm ultimately not qualified to make such claims, so I seem to have to approach this by sharing technical details to the best of my ability. Broadly speaking, the goal is to create a secure P2P ecosystem.

Signal doesn't create a webapp for legitimate reasons around how that project is architected. I hope in this approach I can overcome those limitations.

This version of the app demonstrates a fairly unique approach using a browser-based, local-only and webrtc approach. In an evolving field like cybersecurity, I know it's impossible for any system to be the "world's most secure". By rigorously implementing an exhaustive list of security features and practices, the aim is to get as close as possible.

This is intended to demonstrate client-side managed secure cryptography.

Features:

  • Core
    • PWA
    • P2P
    • Local-first / Local-only
    • No installation
    • TURN server
    • Encrypted-at-rest
  • WhatsApp clone
    • End to end encryption
    • Signal protocol
    • PQ cryptography
    • Multimedia
    • File transfer
    • Video calls
  • Nextcloud clone
    • file-transfer
    • Encrypted vault
    • folder sync
  • EuroOffice clone
    • Word
    • Spreadsheet
    • PDF
    • Code

More open source examples of the core concepts can be seen in the docs. There are several similar projects which may make it confusing, so feel free to reach out for clarity instead of diving into the code/docs.

IMPORTANT: While this is aiming to provide a secure experience, it isnt audited. Shared for testing, feedback and demo purposes only. Please use responsibly.

FAQ:

  • Audit?
  • EU Chat control?
  • Production-ready?
    • No, for testing and demo purposes only. It would be great to get feedback for improvements to get production-ready.
  • Paywall?
    • Its completly free and unlimited to use. The free and paid plans on clerk are currently the same experience.
reddit.com
u/Accurate-Screen8774 — 25 days ago