#peertopeer — Public Fediverse posts

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

Sality-Botnetz nach mehr als 20 Jahren durch Sinkhole-Aktion gestoppt

Ein Peer-to-Peer-Netzwerk aus infizierten Rechnern, das seit dem Jahr 2003 bestand, ist nicht mehr unter der Kontrolle seines Betreibers.

https://www.all-about-security.de/sality-botnetz-nach-mehr-als-20-jahren-durch-sinkhole-aktion-gestoppt/

#botnet #peertopeer #malware

Notes on Private Trackers

https://www.jenn.site/notes-on-private-trackers/

Comments: https://news.ycombinator.com/item?id=49450382

#HackerNews #privateTrackers #peerToPeer #privacy #onlineSecurity #fileSharing

Notes on Private Trackers

https://www.jenn.site/notes-on-private-trackers/

Comments: https://news.ycombinator.com/item?id=49450382

#HackerNews #privateTrackers #peerToPeer #privacy #onlineSecurity #fileSharing

Notes on Private Trackers

https://www.jenn.site/notes-on-private-trackers/

Comments: https://news.ycombinator.com/item?id=49450382

#HackerNews #privateTrackers #peerToPeer #privacy #onlineSecurity #fileSharing

Notes on Private Trackers

https://www.jenn.site/notes-on-private-trackers/

Comments: https://news.ycombinator.com/item?id=49450382

#HackerNews #privateTrackers #peerToPeer #privacy #onlineSecurity #fileSharing

Notes on Private Trackers

https://www.jenn.site/notes-on-private-trackers/

Comments: https://news.ycombinator.com/item?id=49450382

#HackerNews #privateTrackers #peerToPeer #privacy #onlineSecurity #fileSharing

Iroh: Peer to peer networking tools
https://www.iroh.computer/
#distributed #networking #opensource #peertopeer #p2p #+

Iroh: Peer to peer networking tools
https://www.iroh.computer/
#distributed #networking #opensource #peertopeer #p2p #+

Iroh: Peer to peer networking tools
https://www.iroh.computer/
#distributed #networking #opensource #peertopeer #p2p #+

Iroh: Peer to peer networking tools
https://www.iroh.computer/
#distributed #networking #opensource #peertopeer #p2p #+

RT @hasantoxr: Google hat gerade etwas Großes für Agenten-Entwickler stillschweigend veröffentlicht. Es heißt SAM: Sovereign Agent Mesh. Ein Peer-to-Peer-Netzwerk, in dem KI-Agenten einander automatisch entdecken, jedes Paket authentifizieren und Tools über das gesamte Mesh aufrufen, ohne einen zentralen Server. Stellen Sie es sich wie BitTorrent vor, aber für Ihre Agenten. Derzeit ist jeder Agenten-Stack, den Sie aufbauen, ein abgeschlossener Garten. Claude Code kommuniziert mit seinen MCPs. Codex kommuniziert mit seinen MCPs. Wenn Sie wollen, dass Agenten, die auf Ihrem Laptop, Ihrem VPS und Ihrem Mac Studio laufen, Tools miteinander teilen, verkleben Sie SSH-Tunnel und REST-Endpunkte wie im Jahr 2015 zusammen. SAM lässt diese gesamte Schicht verschwinden. Sie führen einen sam-node auf jeder Maschine aus, und die Knoten finden einander automatisch. Jede Verbindung ist kryptografisch identifiziert, sodass Ihre Agenten sich einstecken und Tools im gesamten Netzwerk aufrufen können. Die Identität ist ebenfalls portabel. Derselbe Knoten, dieselben Schlüssel, egal ob auf GCP, Ihrem Laptop oder einem Raspberry Pi im Schrank. Wenn Sie es ernst meinen mit dem Betrieb von Agenten über mehrere Geräte hinweg, nehmen Sie an diesem Wochenende am Testnetz teil: 1. Installieren Sie sam-node (Binary oder Docker). 2. Richten Sie es auf bananas.sam-mesh.dev. 3. Verbinden Sie Claude oder Gemini mit Ihrem lokalen MCP-Endpunkt. 4. Sehen Sie zu, wie Ihr Agent Tools auf den Knoten anderer Personen entdeckt. Noch früh. Nicht offiziell von Google unterstützt. Dies ist die Richtung, in die sich der Agenten-Stack…

mehr auf Arint.info

#AgentStack #AIAgents #Google #PeerToPeer #SAM #SovereignAgentMesh #arint_info

https://x.com/hasantoxr/status/2091203199877468287

RT @hasantoxr: Google hat gerade etwas Großes für Agenten-Entwickler stillschweigend veröffentlicht. Es heißt SAM: Sovereign Agent Mesh. Ein Peer-to-Peer-Netzwerk, in dem KI-Agenten einander automatisch entdecken, jedes Paket authentifizieren und Tools über das gesamte Mesh aufrufen, ohne einen zentralen Server. Stellen Sie es sich wie BitTorrent vor, aber für Ihre Agenten. Derzeit ist jeder Agenten-Stack, den Sie aufbauen, ein abgeschlossener Garten. Claude Code kommuniziert mit seinen MCPs. Codex kommuniziert mit seinen MCPs. Wenn Sie wollen, dass Agenten, die auf Ihrem Laptop, Ihrem VPS und Ihrem Mac Studio laufen, Tools miteinander teilen, verkleben Sie SSH-Tunnel und REST-Endpunkte wie im Jahr 2015 zusammen. SAM lässt diese gesamte Schicht verschwinden. Sie führen einen sam-node auf jeder Maschine aus, und die Knoten finden einander automatisch. Jede Verbindung ist kryptografisch identifiziert, sodass Ihre Agenten sich einstecken und Tools im gesamten Netzwerk aufrufen können. Die Identität ist ebenfalls portabel. Derselbe Knoten, dieselben Schlüssel, egal ob auf GCP, Ihrem Laptop oder einem Raspberry Pi im Schrank. Wenn Sie es ernst meinen mit dem Betrieb von Agenten über mehrere Geräte hinweg, nehmen Sie an diesem Wochenende am Testnetz teil: 1. Installieren Sie sam-node (Binary oder Docker). 2. Richten Sie es auf bananas.sam-mesh.dev. 3. Verbinden Sie Claude oder Gemini mit Ihrem lokalen MCP-Endpunkt. 4. Sehen Sie zu, wie Ihr Agent Tools auf den Knoten anderer Personen entdeckt. Noch früh. Nicht offiziell von Google unterstützt. Dies ist die Richtung, in die sich der Agenten-Stack…

mehr auf Arint.info

#AgentStack #AIAgents #Google #PeerToPeer #SAM #SovereignAgentMesh #arint_info

https://x.com/hasantoxr/status/2091203199877468287

RT @hasantoxr: Google hat gerade etwas Großes für Agenten-Entwickler stillschweigend veröffentlicht. Es heißt SAM: Sovereign Agent Mesh. Ein Peer-to-Peer-Netzwerk, in dem KI-Agenten einander automatisch entdecken, jedes Paket authentifizieren und Tools über das gesamte Mesh aufrufen, ohne einen zentralen Server. Stellen Sie es sich wie BitTorrent vor, aber für Ihre Agenten. Derzeit ist jeder Agenten-Stack, den Sie aufbauen, ein abgeschlossener Garten. Claude Code kommuniziert mit seinen MCPs. Codex kommuniziert mit seinen MCPs. Wenn Sie wollen, dass Agenten, die auf Ihrem Laptop, Ihrem VPS und Ihrem Mac Studio laufen, Tools miteinander teilen, verkleben Sie SSH-Tunnel und REST-Endpunkte wie im Jahr 2015 zusammen. SAM lässt diese gesamte Schicht verschwinden. Sie führen einen sam-node auf jeder Maschine aus, und die Knoten finden einander automatisch. Jede Verbindung ist kryptografisch identifiziert, sodass Ihre Agenten sich einstecken und Tools im gesamten Netzwerk aufrufen können. Die Identität ist ebenfalls portabel. Derselbe Knoten, dieselben Schlüssel, egal ob auf GCP, Ihrem Laptop oder einem Raspberry Pi im Schrank. Wenn Sie es ernst meinen mit dem Betrieb von Agenten über mehrere Geräte hinweg, nehmen Sie an diesem Wochenende am Testnetz teil: 1. Installieren Sie sam-node (Binary oder Docker). 2. Richten Sie es auf bananas.sam-mesh.dev. 3. Verbinden Sie Claude oder Gemini mit Ihrem lokalen MCP-Endpunkt. 4. Sehen Sie zu, wie Ihr Agent Tools auf den Knoten anderer Personen entdeckt. Noch früh. Nicht offiziell von Google unterstützt. Dies ist die Richtung, in die sich der Agenten-Stack…

mehr auf Arint.info

#AgentStack #AIAgents #Google #PeerToPeer #SAM #SovereignAgentMesh #arint_info

https://x.com/hasantoxr/status/2091203199877468287

#TikTok is reportedly developing a #peertopeer #payment feature within its #directmessaging system, utilising its existing #TikTokPay offering. This feature, currently in early development, would allow users to send money to each other, similar to Venmo. https://techcrunch.com/2026/08/18/tiktok-explores-peer-to-peer-payments-via-dms-report-says/?eicker.news #tech #news #ainews

#TikTok is reportedly developing a #peertopeer #payment feature within its #directmessaging system, utilising its existing #TikTokPay offering. This feature, currently in early development, would allow users to send money to each other, similar to Venmo. https://techcrunch.com/2026/08/18/tiktok-explores-peer-to-peer-payments-via-dms-report-says/?eicker.news #tech #news #ainews

#TikTok is reportedly developing a #peertopeer #payment feature within its #directmessaging system, utilising its existing #TikTokPay offering. This feature, currently in early development, would allow users to send money to each other, similar to Venmo. https://techcrunch.com/2026/08/18/tiktok-explores-peer-to-peer-payments-via-dms-report-says/?eicker.news #tech #news #ainews

#TikTok is reportedly developing a #peertopeer #payment feature within its #directmessaging system, utilising its existing #TikTokPay offering. This feature, currently in early development, would allow users to send money to each other, similar to Venmo. https://techcrunch.com/2026/08/18/tiktok-explores-peer-to-peer-payments-via-dms-report-says/?eicker.news #tech #news #ainews

#TikTok is reportedly developing a #peertopeer #payment feature within its #directmessaging system, utilising its existing #TikTokPay offering. This feature, currently in early development, would allow users to send money to each other, similar to Venmo. https://techcrunch.com/2026/08/18/tiktok-explores-peer-to-peer-payments-via-dms-report-says/?eicker.news #tech #news #ainews

Shorter loops, stronger proof.

Reports → reviewed changes. Commits → independent mirrors. Faster, clearer, harder to mistake for finished work before the proof is there.

AI-generated; occasional AI posts.

#ForkMesh #OpenSource #FOSS #DevTools #Git #SelfHosted #Decentralized #DevOps #Programming #Developers #Coding #GitOps #Infra #DistributedSystems #PeerToPeer #Tech #Engineering #OSS #CodeReview #IndieWeb #Federation #SoftwareFreedom #DigitalSovereignty #BuildInPublic
https://forkmesh.com/blog/shorter-loops-stronger-proof/

Shorter loops, stronger proof.

Reports → reviewed changes. Commits → independent mirrors. Faster, clearer, harder to mistake for finished work before the proof is there.

AI-generated; occasional AI posts.

#ForkMesh #OpenSource #FOSS #DevTools #Git #SelfHosted #Decentralized #DevOps #Programming #Developers #Coding #GitOps #Infra #DistributedSystems #PeerToPeer #Tech #Engineering #OSS #CodeReview #IndieWeb #Federation #SoftwareFreedom #DigitalSovereignty #BuildInPublic
https://forkmesh.com/blog/shorter-loops-stronger-proof/

Shorter loops, stronger proof.

Reports → reviewed changes. Commits → independent mirrors. Faster, clearer, harder to mistake for finished work before the proof is there.

AI-generated; occasional AI posts.

#ForkMesh #OpenSource #FOSS #DevTools #Git #SelfHosted #Decentralized #DevOps #Programming #Developers #Coding #GitOps #Infra #DistributedSystems #PeerToPeer #Tech #Engineering #OSS #CodeReview #IndieWeb #Federation #SoftwareFreedom #DigitalSovereignty #BuildInPublic
https://forkmesh.com/blog/shorter-loops-stronger-proof/

Shorter loops, stronger proof.

Reports → reviewed changes. Commits → independent mirrors. Faster, clearer, harder to mistake for finished work before the proof is there.

AI-generated; occasional AI posts.

#ForkMesh #OpenSource #FOSS #DevTools #Git #SelfHosted #Decentralized #DevOps #Programming #Developers #Coding #GitOps #Infra #DistributedSystems #PeerToPeer #Tech #Engineering #OSS #CodeReview #IndieWeb #Federation #SoftwareFreedom #DigitalSovereignty #BuildInPublic
https://forkmesh.com/blog/shorter-loops-stronger-proof/

Shorter loops, stronger proof.

Reports → reviewed changes. Commits → independent mirrors. Faster, clearer, harder to mistake for finished work before the proof is there.

AI-generated; occasional AI posts.

#ForkMesh #OpenSource #FOSS #DevTools #Git #SelfHosted #Decentralized #DevOps #Programming #Developers #Coding #GitOps #Infra #DistributedSystems #PeerToPeer #Tech #Engineering #OSS #CodeReview #IndieWeb #Federation #SoftwareFreedom #DigitalSovereignty #BuildInPublic
https://forkmesh.com/blog/shorter-loops-stronger-proof/

Exploring the new peer-to-peer Internet.

It's not the fanciest thing to look at now, but the interesting work is happening at the lower levels of the OSI network model at the moment.

#Reticulum #MeshNetworking #PeerToPeer

Exploring the new peer-to-peer Internet.

It's not the fanciest thing to look at now, but the interesting work is happening at the lower levels of the OSI network model at the moment.

#Reticulum #MeshNetworking #PeerToPeer

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

Заметки Note: P2P-синхронизация, локальное шифрование и режим «под принуждением»

По-настоящему важные данные нельзя держать в одном единственном месте — их нужно диверсифицировать. Можно хранить всё дома и однажды вернуться с прогулки, а вместо дома и драгоценного компьютера — одни обугленные руины. Можно носить всё с собой в телефоне, но лишиться его в первом же кафе, где аппарат вытащит у вас из кармана воришка. Можно загрузить всё на надёжный сервер крупной корпорации, но в один прекрасный день эта корпорация введёт против вас санкции или просто заблокирует доступ к вашему же аккаунту. У каждого отдельного хранилища есть свой собственный способ вас подвести. Вот ровно эту проблему я и попытался решить.

https://habr.com/ru/articles/1060536/

#заметки #синхронизация #шифрование #peertopeer #криптография #информационная_безопасность #TPM #Android_Keystore #open_source #кроссплатформенность

Заметки Note: P2P-синхронизация, локальное шифрование и режим «под принуждением»

По-настоящему важные данные нельзя держать в одном единственном месте — их нужно диверсифицировать. Можно хранить всё дома и однажды вернуться с прогулки, а вместо дома и драгоценного компьютера — одни обугленные руины. Можно носить всё с собой в телефоне, но лишиться его в первом же кафе, где аппарат вытащит у вас из кармана воришка. Можно загрузить всё на надёжный сервер крупной корпорации, но в один прекрасный день эта корпорация введёт против вас санкции или просто заблокирует доступ к вашему же аккаунту. У каждого отдельного хранилища есть свой собственный способ вас подвести. Вот ровно эту проблему я и попытался решить.

https://habr.com/ru/articles/1060536/

#заметки #синхронизация #шифрование #peertopeer #криптография #информационная_безопасность #TPM #Android_Keystore #open_source #кроссплатформенность

Заметки Note: P2P-синхронизация, локальное шифрование и режим «под принуждением»

По-настоящему важные данные нельзя держать в одном единственном месте — их нужно диверсифицировать. Можно хранить всё дома и однажды вернуться с прогулки, а вместо дома и драгоценного компьютера — одни обугленные руины. Можно носить всё с собой в телефоне, но лишиться его в первом же кафе, где аппарат вытащит у вас из кармана воришка. Можно загрузить всё на надёжный сервер крупной корпорации, но в один прекрасный день эта корпорация введёт против вас санкции или просто заблокирует доступ к вашему же аккаунту. У каждого отдельного хранилища есть свой собственный способ вас подвести. Вот ровно эту проблему я и попытался решить.

https://habr.com/ru/articles/1060536/

#заметки #синхронизация #шифрование #peertopeer #криптография #информационная_безопасность #TPM #Android_Keystore #open_source #кроссплатформенность

Anyone used #RetroShare / @xeres before ?

#Question #Mastodon

#P2P #Share #Files #retro #Email #messages directly #PeerToPeer #Encrypted #Decentralised ( etc )

#Windows + #Linux + #macOS + #Android client

https://retroshare.cc
https://xeres.io/

Anyone used #RetroShare / @xeres before ?

#Question #Mastodon

#P2P #Share #Files #retro #Email #messages directly #PeerToPeer #Encrypted #Decentralised ( etc )

#Windows + #Linux + #macOS + #Android client

https://retroshare.cc
https://xeres.io/

Anyone used #RetroShare / @xeres before ?

#Question #Mastodon

#P2P #Share #Files #retro #Email #messages directly #PeerToPeer #Encrypted #Decentralised ( etc )

#Windows + #Linux + #macOS + #Android client

https://retroshare.cc
https://xeres.io/

Anyone used #RetroShare / @xeres before ?

#Question #Mastodon

#P2P #Share #Files #retro #Email #messages directly #PeerToPeer #Encrypted #Decentralised ( etc )

#Windows + #Linux + #macOS + #Android client

https://retroshare.cc
https://xeres.io/

Anyone used #RetroShare / @xeres before ?

#Question #Mastodon

#P2P #Share #Files #retro #Email #messages directly #PeerToPeer #Encrypted #Decentralised ( etc )

#Windows + #Linux + #macOS + #Android client

https://retroshare.cc
https://xeres.io/

The future of p2p is NOW (and here, with this people)

Aw it’s happening for real

@gwil @adz @cwebber @matthew @dholms.at

#p2p #DWebCamp #peerToPeer

The future of p2p is NOW (and here, with this people)

Aw it’s happening for real

@gwil @adz @cwebber @matthew @dholms.at

#p2p #DWebCamp #peerToPeer

The future of p2p is NOW (and here, with this people)

Aw it’s happening for real

@gwil @adz @cwebber @matthew @dholms.at

#p2p #DWebCamp #peerToPeer

The future of p2p is NOW (and here, with this people)

Aw it’s happening for real

@gwil @adz @cwebber @matthew @dholms.at

#p2p #DWebCamp #peerToPeer

The future of p2p is NOW (and here, with this people)

Aw it’s happening for real

@gwil @adz @cwebber @matthew @dholms.at

#p2p #DWebCamp #peerToPeer

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://Enkrypted.Chat

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://Enkrypted.Chat

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