home.social

#peerjs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #peerjs, aggregated by home.social.

  1. #Encrypted #P2P #Messaging App

    Want to send #E2E encrypted messages and #video #calls with no downloads, no sign-ups and no tracking?

    This prototype uses #PeerJS to establish a secure browser-to-browser connection. Using browser-only storage—true #zerodata #privacy!

    Https://enkrypted.chat

    The aim is to have an experience as close to Whatsapp as reasonably possible so that the experience is intuitive.

    Some features include:

    P2P

    End to end encryption

    Browser-based

    No installation/registration

    Messaging

    Text Messaging

    Multimedia Messaging

    File Transfer

    Video Calls

    Data Ownership

    passkeys-based encryption

    Local-Only storage

    Encrypted at rest

    NOTE: This is still a work-in-progress and a close-source project. To view the open source MVP see here. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    Reddit: reddit.com/r/positive//_intent

    Mastodon: infosec.exchange/@xoron

    Docs: positive-intentions.com

  2. #Encrypted #P2P #Messaging App

    Want to send #E2E encrypted messages and #video #calls with no downloads, no sign-ups and no tracking?

    This prototype uses #PeerJS to establish a secure browser-to-browser connection. Using browser-only storage—true #zerodata #privacy!

    Https://enkrypted.chat

    The aim is to have an experience as close to Whatsapp as reasonably possible so that the experience is intuitive.

    Some features include:

    P2P

    End to end encryption

    Browser-based

    No installation/registration

    Messaging

    Text Messaging

    Multimedia Messaging

    File Transfer

    Video Calls

    Data Ownership

    passkeys-based encryption

    Local-Only storage

    Encrypted at rest

    NOTE: This is still a work-in-progress and a close-source project. To view the open source MVP see here. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    Reddit: reddit.com/r/positive//_intent

    Mastodon: infosec.exchange/@xoron

    Docs: positive-intentions.com

  3. #Encrypted #P2P #Messaging App

    Want to send #E2E encrypted messages and #video #calls with no downloads, no sign-ups and no tracking?

    This prototype uses #PeerJS to establish a secure browser-to-browser connection. Using browser-only storage—true #zerodata #privacy!

    Https://enkrypted.chat

    The aim is to have an experience as close to Whatsapp as reasonably possible so that the experience is intuitive.

    Some features include:

    P2P

    End to end encryption

    Browser-based

    No installation/registration

    Messaging

    Text Messaging

    Multimedia Messaging

    File Transfer

    Video Calls

    Data Ownership

    passkeys-based encryption

    Local-Only storage

    Encrypted at rest

    NOTE: This is still a work-in-progress and a close-source project. To view the open source MVP see here. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    Reddit: reddit.com/r/positive//_intent

    Mastodon: infosec.exchange/@xoron

    Docs: positive-intentions.com

  4. glitr.positive-intentions.com

    Secure decentralized P2P messaging PWA

    Progress update:

    - UI improvements throughout
    - Passkey-based encrypted data at rest.
    - Introducing giphy integration
    - Bug fixes throughout

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen here: github.com/positive-intentions. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging #PWA

  5. glitr.positive-intentions.com

    Secure decentralized P2P messaging PWA

    Progress update:

    - UI improvements throughout
    - Passkey-based encrypted data at rest.
    - Introducing giphy integration
    - Bug fixes throughout

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen here: github.com/positive-intentions. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging #PWA

  6. glitr.positive-intentions.com

    Secure decentralized P2P messaging PWA

    Progress update:

    - UI improvements throughout
    - Passkey-based encrypted data at rest.
    - Introducing giphy integration
    - Bug fixes throughout

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen here: github.com/positive-intentions. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging #PWA

  7. glitr.positive-intentions.com

    Secure decentralized P2P messaging PWA

    Progress update:

    - UI improvements throughout
    - Passkey-based encrypted data at rest.
    - Introducing giphy integration
    - Bug fixes throughout

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen here: github.com/positive-intentions. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging #PWA

  8. glitr.positive-intentions.com

    Secure decentralized P2P messaging PWA

    Progress update:

    - UI improvements throughout
    - Passkey-based encrypted data at rest.
    - Introducing giphy integration
    - Bug fixes throughout

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen here: github.com/positive-intentions. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging #PWA

  9. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  10. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  11. E2EE P2P Messaging App

    I recently introduced [metered.ca](metered.ca) for the STUN/TURN servers and the stability has hugely improved and so i'd like to ask for your feedback if you'd like to try it out.

    Demo: p2p.positive-intentions.com/if

    Data isnt persisted (yet), so each page refresh will clear all keys.

    (IMPORTANT: For testing and demo purposes only. This is a work-in-progress and far from finished. It has not been reviewed or audited. Do not use it for sensitive data.)

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #Encrypted #infosec #cryptography #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #WebDev #TechDevelopment #ChatApp #javascript #InstantMessaging

  12. Want to send messages and video calls with:

    * no installs
    * no sign-ups
    * no tracking
    * end-to-end encryption

    This new prototype uses PeerJS to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the [testable demo here](p2p.positive-intentions.com/if).

    I am working towards a look-and-feel to match Whatsapp as seen in this [hardcoded UI demo](glitr.positive-intentions.com).

    IMPORTANT NOTE: This is still a work-in-progress and a close-source project. It is based on the open source MVP see [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive_intentio
    * GitHub: github.com/positive-intentions

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  13. id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.

    github.com/positive-intentions

    positive-intentions.com/blog/i

    im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.

    using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.

    - i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).

    - another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.

    - to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.

    - i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)

    - the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.

    i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.

    while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.

    (note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)

  14. I can't seem to coerce nginx and npm to play together nicely. I'm running a proxy to access a different port for 443 on one site. It can't find the node_modules directory automatically. What works in a 127.0.0.1 environment fails on a production server with nginx in the way.

    Maybe I can get the 127.0.0.1 code and the production code talking to each other. I think nginx is acting where peerjs should be. Will this solve anything? We'll find out soon. Plan A is giving me a headache.

    #npm #peerjs #nginx

  15. Hey chooms, are any of you interested in collaborating on a serverless peer-to-peer (WebRTC) implementation of Nine Men's Morris? (Especially e.g. asset contribution, UI design...also happy for code and architecture contribution). It's in typescript/sveltekit

    I started it as a way to mess around with Zero trust serverless gaming (a broker is still required just for peer discovery) I think I'm mostly done with the game architecture and how turn validation should work without having to trust your peer.

    Have a look and see what you think:

    github.com/zeyus/nine-peers-mo

    github.com/zeyus/nine-peers-mo

    #opensource #gamedev #serverless #oss #WebDev #WebDevelopment #WebDesign #ux #ui #svelte #sveltekit #TypeScript #peerjs #webrtc

  16. I'm slowly having fun with #webRTC and #peerJS. The chat app that was originally intended for #KaiOS is now online as a website: flop.bhackers.uber.space/#!/in, so it can also be used as a web app for other operating systems. Communication between two users is still simple, but a group chat is a bit more complicated.

  17. Thank you #peerjs for restoring my faith and fun in my web project and helping me stay focused.

  18. The only think I haven't tackled is STUN/TURN/ICE servers. With my simple test I didn't seem to need them with . Curious if other developers have any input on when they'll be needed.

  19. I spent the weekend learning to experiment with ... and I love it! It's dead simple, and I'm beginning to see how this might be useful for various p2p data sharing.

  20. id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.

    github.com/positive-intentions

    positive-intentions.com/blog/i

    im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.

    using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.

    - i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).

    - another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.

    - to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.

    - i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)

    - the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.

    i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.

    while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.

    (note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)

  21. id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.

    github.com/positive-intentions

    positive-intentions.com/blog/i

    im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.

    using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.

    - i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).

    - another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.

    - to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.

    - i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)

    - the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.

    i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.

    while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.

    (note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)

  22. id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.

    github.com/positive-intentions

    positive-intentions.com/blog/i

    im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.

    using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.

    - i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).

    - another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.

    - to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.

    - i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)

    - the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.

    i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.

    while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.

    (note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)

  23. id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.

    github.com/positive-intentions

    positive-intentions.com/blog/i

    im not an expert on #cyberSecurity. im sure there are many gaps in my knowlege in this domain.

    using #javascript, i initially created a fairly basic #chatApp using using #peerjs to create #encrypted #webrtc #connections. this was then easily enhanced by exchanging additional #encryption #keys from #cryptography functions built into browsers (#webcrypto api) to add a redundent layer of encryption. a #diffieHelman key #exchange is done over #webrtc (which can be considered #secure when exchanged over public channels) to create #serverless #p2p #authentication.

    - i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have #openedSource my #cryptography module. its basically a thin wrapper around vanilla cryptography functions of a #browser (webcrypto api).

    - another concern for my kind of app (#PWA) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for #selfhosting. selhosting this app has some unique features. unlike many other #selfhosted #projects, this app can be hosted on #githubPages (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.

    - to prevent things like browser extensions, the app uses strict #CSP headers to prevent #unauthorised code from running. #selfhosting users should take note of this when setting up their own instance.

    - i received feedback the #Signal/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the #complexity by working with #webrtc. while it has its many flaws, i think risks can be reasonable mitigated if the #cryptography functions are implemented correctly. (all data out is #encrypted and all data in is #decrypted on-the-fly)

    - the key detail that makes this approach unique, is because as a #webapp, unlike other solutions, users have a choice of using any #device/#os/#browser. while a webapp can have nuanced #vulnerabilities, i think by #openSourcing and providing instructions for #selfhosting and instructions to #build for various #platforms, it can provide a reasonable level of #security.

    i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the #frontend and the peerjs-server to be #hosted #independently, im on track for creating a #chatSystem with the "fewest moving parts". i hope you will agree this is true #p2p and i hope i can use this as a step towards true #privacy and #security. #security might be further improved by using a trusted #VPN.

    while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find #bestPractices for the functionalities i want to achieve. in particular #security practices to use when using #p2p technology.

    (note: this app is an #unstable, #experiment, #proofOfConcept and not ready to replace any other app or service. It's far from finished and provided for #testing and #demo purposes only. This post is to get #feedback on the progress to determine if i'm going in the right direction for a secure chat app)

  24. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  25. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  26. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  27. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  28. I just created a new webapp! Manipulate 3D models in #vr / #xr and automatically sync the scene with a computer. People can also join the collaboration on their phones.

    The idea is that you can load one or more models located on your computer, send them to the VR headset (synced #p2p ), arrange them with your hands, then go back to the scene on your computer.

    Built with #threejs #webxr #peerjs
    akodiat.github.io/xrView/

  29. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  30. Want E2E encrypted messages and video calls with no downloads, no sign-ups and no tracking?

    This prototype uses webRTC to establish a secure browser-to-browser connection. Everything is ephemeral and cleared when you refresh the page—true zerodata privacy!

    Check out the pre-release demo here: p2p.positive-intentions.com/if

    (For those who have seen it before, i've added fixes and improvements throughout, so it might still be worth checking out)

    NOTE: This is still a work-in-progress and a close-source project. Its far from finished and doesnt have the user-experience needed to promote the project to a wider audience. The implementation is based on the open source MVP seen [here](github.com/positive-intentions). It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app.

    * Docs: positive-intentions.com/docs/c
    * Reddit: reddit.com/r/positive/_intenti
    * More: positive-intentions.com

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #CloseSource #OpenSource #WebDev #GitHub #TechDevelopment #WhatsApp #ChatApp #InstantMessaging

  31. E2EE P2P Messaging App

    I recently introduced [metered.ca](metered.ca) for the STUN/TURN servers and the stability has hugely improved and so i'd like to ask for your feedback if you'd like to try it out.

    Demo: p2p.positive-intentions.com/if

    Data isnt persisted (yet), so each page refresh will clear all keys.

    (IMPORTANT: For testing and demo purposes only. This is a work-in-progress and far from finished. It has not been reviewed or audited. Do not use it for sensitive data.)

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #Encrypted #infosec #cryptography #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #WebDev #TechDevelopment #ChatApp #javascript #InstantMessaging

  32. E2EE P2P Messaging App

    I recently introduced [metered.ca](metered.ca) for the STUN/TURN servers and the stability has hugely improved and so i'd like to ask for your feedback if you'd like to try it out.

    Demo: p2p.positive-intentions.com/if

    Data isnt persisted (yet), so each page refresh will clear all keys.

    (IMPORTANT: For testing and demo purposes only. This is a work-in-progress and far from finished. It has not been reviewed or audited. Do not use it for sensitive data.)

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #Encrypted #infosec #cryptography #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #WebDev #TechDevelopment #ChatApp #javascript #InstantMessaging

  33. E2EE P2P Messaging App

    I recently introduced [metered.ca](metered.ca) for the STUN/TURN servers and the stability has hugely improved and so i'd like to ask for your feedback if you'd like to try it out.

    Demo: p2p.positive-intentions.com/if

    Data isnt persisted (yet), so each page refresh will clear all keys.

    (IMPORTANT: For testing and demo purposes only. This is a work-in-progress and far from finished. It has not been reviewed or audited. Do not use it for sensitive data.)

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #Encrypted #infosec #cryptography #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #WebDev #TechDevelopment #ChatApp #javascript #InstantMessaging

  34. E2EE P2P Messaging App

    I recently introduced [metered.ca](metered.ca) for the STUN/TURN servers and the stability has hugely improved and so i'd like to ask for your feedback if you'd like to try it out.

    Demo: p2p.positive-intentions.com/if

    Data isnt persisted (yet), so each page refresh will clear all keys.

    (IMPORTANT: For testing and demo purposes only. This is a work-in-progress and far from finished. It has not been reviewed or audited. Do not use it for sensitive data.)

    #P2P #WebRTC #PeerJS #ZeroData #EphemeralData #Encryption #Encrypted #infosec #cryptography #E2EE #BrowserToBrowser #NoInstall #Privacy #Security #Decentralized #Messaging #VideoCall #NoTracking #PrivateMessaging #Prototype #Demo #WorkInProgress #WebDev #TechDevelopment #ChatApp #javascript #InstantMessaging

  35. I can't seem to coerce nginx and npm to play together nicely. I'm running a proxy to access a different port for 443 on one site. It can't find the node_modules directory automatically. What works in a 127.0.0.1 environment fails on a production server with nginx in the way.

    Maybe I can get the 127.0.0.1 code and the production code talking to each other. I think nginx is acting where peerjs should be. Will this solve anything? We'll find out soon. Plan A is giving me a headache.

    #npm #peerjs #nginx