#noregistration — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #noregistration, aggregated by home.social.
-
Secure and Private Decentralized P2P Encrypted Messaging over Git and WebRTC
This project demonstates a unique approach to secure messaging. The approach is different enough that it can't be easily compared to Signal or SimpleX.
The core philosophy around secure messaging here is that it can work in a way that avoids installation and registration by enabling users to host their own data.
The project is far from finished, but im putting together some docs for the "how it works". It's pretty outside-the-box thinking (and that doesnt make it a good idea), so it would be great if you could share your thoughts on the approach.
Website: Glitr.io
Features:
WebApp
P2P / WebRTC
Local-first / Local-only
No installation
TURN server
Encrypted-at-rest
Signal protocol
Post Quantum cryptography
Video calls
TOR / anonymous via Git
Serverless over WebRTC#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #SelfHosted #BuildInPublic #IndieDev #DevCommunity
-
Secure and Private Decentralized P2P Encrypted Messaging over Git and WebRTC
This project demonstates a unique approach to secure messaging. The approach is different enough that it can't be easily compared to Signal or SimpleX.
The core philosophy around secure messaging here is that it can work in a way that avoids installation and registration by enabling users to host their own data.
The project is far from finished, but im putting together some docs for the "how it works". It's pretty outside-the-box thinking (and that doesnt make it a good idea), so it would be great if you could share your thoughts on the approach.
Website: Glitr.io
Features:
WebApp
P2P / WebRTC
Local-first / Local-only
No installation
TURN server
Encrypted-at-rest
Signal protocol
Post Quantum cryptography
Video calls
TOR / anonymous via Git
Serverless over WebRTC#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #SelfHosted #BuildInPublic #IndieDev #DevCommunity
-
Secure and Private Decentralized P2P Encrypted Messaging over Git and WebRTC
This project demonstates a unique approach to secure messaging. The approach is different enough that it can't be easily compared to Signal or SimpleX.
The core philosophy around secure messaging here is that it can work in a way that avoids installation and registration by enabling users to host their own data.
The project is far from finished, but im putting together some docs for the "how it works". It's pretty outside-the-box thinking (and that doesnt make it a good idea), so it would be great if you could share your thoughts on the approach.
Website: Glitr.io
Features:
WebApp
P2P / WebRTC
Local-first / Local-only
No installation
TURN server
Encrypted-at-rest
Signal protocol
Post Quantum cryptography
Video calls
TOR / anonymous via Git
Serverless over WebRTC#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #SelfHosted #BuildInPublic #IndieDev #DevCommunity
-
Secure and Private Decentralized P2P Encrypted Messaging over Git and WebRTC
This project demonstates a unique approach to secure messaging. The approach is different enough that it can't be easily compared to Signal or SimpleX.
The core philosophy around secure messaging here is that it can work in a way that avoids installation and registration by enabling users to host their own data.
The project is far from finished, but im putting together some docs for the "how it works". It's pretty outside-the-box thinking (and that doesnt make it a good idea), so it would be great if you could share your thoughts on the approach.
Website: Glitr.io
Features:
WebApp
P2P / WebRTC
Local-first / Local-only
No installation
TURN server
Encrypted-at-rest
Signal protocol
Post Quantum cryptography
Video calls
TOR / anonymous via Git
Serverless over WebRTC#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #SelfHosted #BuildInPublic #IndieDev #DevCommunity
-
Secure and Private Decentralized P2P Encrypted Messaging over Git and WebRTC
This project demonstates a unique approach to secure messaging. The approach is different enough that it can't be easily compared to Signal or SimpleX.
The core philosophy around secure messaging here is that it can work in a way that avoids installation and registration by enabling users to host their own data.
The project is far from finished, but im putting together some docs for the "how it works". It's pretty outside-the-box thinking (and that doesnt make it a good idea), so it would be great if you could share your thoughts on the approach.
Website: Glitr.io
Features:
WebApp
P2P / WebRTC
Local-first / Local-only
No installation
TURN server
Encrypted-at-rest
Signal protocol
Post Quantum cryptography
Video calls
TOR / anonymous via Git
Serverless over WebRTC#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #SelfHosted #BuildInPublic #IndieDev #DevCommunity
-
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.
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.
* [Enkrypted.Chat](https://enkrypted.chat/)
This is intended to demonstrate client-side managed secure cryptography.
* [Introducing Enkrypted Chat](https://positive-intentions.com/blog/introducing-enkrypted-chat)
* [Whitepaper (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-whitepaper)
* [Protocol Spec (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-protocol-spec)
* [Roadmap](https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown/)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 reviewed](https://www.reddit.com/r/CyberSecurityAdvice/comments/1su8lir/security_audit_feedback_from_radically_open/). **Shared for testing, feedback and demo purposes only.** Please use responsibly.
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
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.
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.
* [Enkrypted.Chat](https://enkrypted.chat/)
This is intended to demonstrate client-side managed secure cryptography.
* [Introducing Enkrypted Chat](https://positive-intentions.com/blog/introducing-enkrypted-chat)
* [Whitepaper (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-whitepaper)
* [Protocol Spec (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-protocol-spec)
* [Roadmap](https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown/)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 reviewed](https://www.reddit.com/r/CyberSecurityAdvice/comments/1su8lir/security_audit_feedback_from_radically_open/). **Shared for testing, feedback and demo purposes only.** Please use responsibly.
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
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.
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.
* [Enkrypted.Chat](https://enkrypted.chat/)
This is intended to demonstrate client-side managed secure cryptography.
* [Introducing Enkrypted Chat](https://positive-intentions.com/blog/introducing-enkrypted-chat)
* [Whitepaper (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-whitepaper)
* [Protocol Spec (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-protocol-spec)
* [Roadmap](https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown/)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 reviewed](https://www.reddit.com/r/CyberSecurityAdvice/comments/1su8lir/security_audit_feedback_from_radically_open/). **Shared for testing, feedback and demo purposes only.** Please use responsibly.
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
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.
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.
* [Enkrypted.Chat](https://enkrypted.chat/)
This is intended to demonstrate client-side managed secure cryptography.
* [Introducing Enkrypted Chat](https://positive-intentions.com/blog/introducing-enkrypted-chat)
* [Whitepaper (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-whitepaper)
* [Protocol Spec (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-protocol-spec)
* [Roadmap](https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown/)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 reviewed](https://www.reddit.com/r/CyberSecurityAdvice/comments/1su8lir/security_audit_feedback_from_radically_open/). **Shared for testing, feedback and demo purposes only.** Please use responsibly.
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
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.
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.
* [Enkrypted.Chat](https://enkrypted.chat/)
This is intended to demonstrate client-side managed secure cryptography.
* [Introducing Enkrypted Chat](https://positive-intentions.com/blog/introducing-enkrypted-chat)
* [Whitepaper (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-whitepaper)
* [Protocol Spec (work-in-progress)](https://positive-intentions.com/docs/technical/whitepaper/complete-protocol-spec)
* [Roadmap](https://positive-intentions.com/docs/technical/p2p-messaging-technical-breakdown/)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 reviewed](https://www.reddit.com/r/CyberSecurityAdvice/comments/1su8lir/security_audit_feedback_from_radically_open/). **Shared for testing, feedback and demo purposes only.** Please use responsibly.
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
I'd like to share the latest version of my project.
It's a a decentralised P2P messaging app. The aim is of course privacy and security.
It demonstrates a fairly unique approach by using browser-based local-only storage with webrtc.
https://www.reddit.com/r/positive_intentions/comments/1tq1u62/introducing_enkrypted_chat
---
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
I'd like to share the latest version of my project.
It's a a decentralised P2P messaging app. The aim is of course privacy and security.
It demonstrates a fairly unique approach by using browser-based local-only storage with webrtc.
https://www.reddit.com/r/positive_intentions/comments/1tq1u62/introducing_enkrypted_chat
---
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
I'd like to share the latest version of my project.
It's a a decentralised P2P messaging app. The aim is of course privacy and security.
It demonstrates a fairly unique approach by using browser-based local-only storage with webrtc.
https://www.reddit.com/r/positive_intentions/comments/1tq1u62/introducing_enkrypted_chat
---
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
I'd like to share the latest version of my project.
It's a a decentralised P2P messaging app. The aim is of course privacy and security.
It demonstrates a fairly unique approach by using browser-based local-only storage with webrtc.
https://www.reddit.com/r/positive_intentions/comments/1tq1u62/introducing_enkrypted_chat
---
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity
-
I'd like to share the latest version of my project.
It's a a decentralised P2P messaging app. The aim is of course privacy and security.
It demonstrates a fairly unique approach by using browser-based local-only storage with webrtc.
https://www.reddit.com/r/positive_intentions/comments/1tq1u62/introducing_enkrypted_chat
---
#Privacy #OnlinePrivacy #DataPrivacy #Infosec #CyberSecurity #OpSec #DigitalRights #AntiSurveillance #DataOwnership #E2EE #P2P #PeerToPeer #WebRTC #LocalFirst #LocalOnly #NoCloud #NoRegistration #PWA #SignalProtocol #PostQuantum #Cryptography #SecureMessaging #PrivateChat #EncryptedChat #Decentralized #OpenSource #SelfHosted #BetaTesting #FeedbackWelcome #TechDemo #ProofOfConcept #BuildInPublic #IndieDev #DevCommunity