r/positive_intentions • • May 28 '26

Introducing: Enkrypted Chat

6 Upvotes

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

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

Features:

  • Core

    • PWA

    • P2P

    • Local-first / Local-only

    • No installation

    • TURN server

    • Encrypted-at-rest

  • WhatsApp clone

    • End to end encryption

    • Signal protocol

    • Post-Quantum cryptography

    • Multimedia

    • File transfer

    • Video calls

  • Nextcloud clone

    • Word

    • Spreadsheet

    • PDF

    • file-transfer

    • Encrypted vault

Some open source versions of the core concepts.

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

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


r/positive_intentions • • Apr 25 '25

Introducing Glitr.io

6 Upvotes

no servers, no accounts, no installs

https://glitr.io

Need to send files privately without the risks of the cloud? Glitr offers serverless, account-free, and install-free direct file sharing. Your data stays between you and your recipient, with no trace left behind.


r/positive_intentions • • Jan 20 '24

A Different Kind of Chat App

6 Upvotes

A chat app that operates in the browser without a backend (kind-of).

The aim is to give users more control over their data, privacy and security. In the interest of transparency, the following are some high-level technical details on how the app works.

Self-Generated and Managed Encryption

With a standard browser, you can create encryption keys and store them on your device, similar to cookies. This is made possible by using tools provided by all modern browsers for cryptography. Check out the code here.

Decentralised Authentication

Our app uses WebRTC to create a secure peer-to-peer connection between two browsers. This connection can persist if the browsers remain connected without a server. With WebRTC, you can send encryption keys between users securely. When you connect to a peer you've previously shared encryptions with, you can validate their identity by checking if they have the same encryption keys you sent in a previous session.

Decentralised Profile

With a JavaScript implementation of symmetric encryption, you can encrypt larger payloads of data. This can be used to encrypt a user's profile, including their username and avatar image.

Decentralised Encrypted Messaging

Our app allows you to store data in the browser, similar to cookies. This can be used to store messages from peers. Browser storage can remain until you decide to clear the site data. Using previously shared encryption keys, you can encrypt messages between peers, with WebRTC providing an extra layer of encryption.

Decentralised Chat

Using Material UI, a popular UI framework with a lot of components, you can create a chat interface. A better UI allows for a more interactive and intuitive app experience.

Decentralised File Transfer

With IndexedDB, you can store large files on your device directly from the browser. The capacity is larger than that used for typical cookies. Symmetric encryption can be used to encrypt these large files, and WebRTC can be used to send files between peers.

Decentralised Virtual Reality

With a standard browser, you can create 3D graphics in the browser with WebGL/WebGPU. This can be used to create a virtual reality environment. You can use WebRTC to share your 3D-position in the virtual environment and to share a live video stream with a peer. This video stream can be used to texture a 3D model in the virtual environment.

We would like your feedback about that app. In particular, we are open to feature requests and bug reports.

Chat App

Getting Started + documentation

r/positive_intentions


r/positive_intentions • • Aug 12 '25

Chat V2

4 Upvotes

Building secure peer-to-peer messaging apps is tough, and it's even tougher to get people to switch from what they already use. I've noticed that a great user interface and an intuitive design often matter more to people than terms like cryptography or end-to-end encryption.

That's why I've started building a UI library to tackle this head-on! It's a work in progress, but the goal is to create a more welcoming and seamless experience for new users.

Check out the UI library here: https://ui.positive-intentions.com

And you can see a live demo of the UI in action here: demo

Its far from finished, but i'd love to hear your thoughts and feedback as I continue to shape it!

(For more information about the new version, check out: https://positive-intentions.com/docs/category/chat-v2)


r/positive_intentions • • Oct 09 '24

Joining the fediverse. Follow on Mastodon.

Thumbnail
infosec.exchange
4 Upvotes

r/positive_intentions • • Feb 14 '24

Adding the "decentralized" to decentralized-chat

4 Upvotes

In response to questions about the decentralization of hosting the app on AWS S3, we would like to introduce a static bundle download of the app. Offering the app in this format allows it to be more accurately described as a decentralized chat app.

For most curious users, we reccommend taking a look at the online S3 hosted version because we've set up some CSP headers to prevent potential issues like browser extensions accessing app data.

However, it's important to note that the app isn't fully open source, so only those who are confident and willing to experiment should host it, as the code is generally opaque due to minification and obfuscation.

It's also worth noting that the app is primarily a proof-of-concept demo meant for testing purposes, so stability isn't guaranteed.

To try out the app, you can visit: https://chat.positive-intentions.com


r/positive_intentions • • Oct 15 '26

Introducing Glitr.io

3 Upvotes

TLDR; Combining TOR, WebRTC and Git into a Decentralized E2EE P2P Messaging App

This is a fairly a unique stack and architecture in contrast to the traditional approach with mainstream messaging apps. To put it briefly, its a Rust-based frontend with a Git-server backend, which can be used to establish a E2EE Tor/WebRTC connection.

Features:

  • No installation

  • No registration

  • PWA

  • Android

  • TUI

  • WebRTC

  • Tor routing

  • TURN server

  • Git-host backend

  • Local-first

  • Encrypted-at-rest

  • Signal protocol

  • Post Quantum cryptography

  • Calls

  • File-transfer

IMPORTANT DISCLAIMER: While this is aiming to provide a secure experience, it's a work-in-progress and far from finished. It is unreviewed and unaudited. I'm sharing here for testing, feedback and demo purposes only. Pease use responsibly.


r/positive_intentions • • Jan 29 '26

Roadmap / Technical Breakdown / "How it works"

3 Upvotes

NOTE: This is still a work-in-progress and far from finished. It is free to use and not sold or monetized in any way. It has NOT been audited or reviewed. For testing purposes only, not a replacement for your current messaging app. I have open source examples of various part of the app and im sure more investigation needs to be done for all details of this project. USE RESPONSIBLY!

Unlike my usual posts along the lines of "promoting my project". I'm aiming for this post to be more technical. I hope to make it clear how the project works and some features/capabilities I will be working on. Feel free to reach out for clarity.

Cyber-security is a constantly evolving field and no system can be completely secure. I tried to create an exhaustive list of features and practices that could help make the messaging app as secure as possible.

Demo

(Im grouping into green, orange and red because i coudnt think of a more appropriate title for the grouping.)

Green

  • P2P - so that it can be decentralized and not rely on a central server for exchanging messages. The project is using WebRTC to establish a p2p connection between browsers.

  • Peer discovery - the ID being used is cryptographically random. its generated automatically client-side and should have good conflict resilience so someone cant guess the ID to connect to you. that ID is used with the peerjs-server (open source, selfhostable), which is being used as the connection broker to establish a webrtc connection.

  • End to end encryption - so that even if the messages are intercepted, they cannot be read. The project is using an application-level cascading cipher on top of the encryption provided by WebRTC. the key sub-protocols involves in the approach are Signal, MLS and AES. while there has been pushback on the cascading cipher, rest-assured that this is functioning on and application-level and the purpose of the cipher is that it guarantees that the "stronger" algoritm comes up on top. any failure will result in a cascading failure... ultimately redundent on top of the mandated WebRTC encryption. i would plan to add more protocols into this cascade to investigate post-quantum solutions.

  • Perfect forward secrecy - so that if a key is compromised, past messages cannot be decrypted. WebRTC already provides a reasonable support for this in firefox. but the signal and mls protocol in the cascading cipher also contribute resiliance in this regard.

  • Key management - so that users can manage their own keys and not rely on a central authority. there is key focus on having local-only encryption keys. sets of keys are generated for each new connection and resued in future sessions.

  • Secure signaling - so that the initial connection between peers is established securely. there are many approaches to secure signaling and while a good approach could be exchanging connection data offline, i would also be further improving this by providing more options. its possible to establish a webrtc connection without a connection-broker like this.

  • Minimal infrastructure - so that there are fewer points of failure and attack. in the Webrtc approach, messages can be sent without the need of a central server and would also work in an offline hotspot network.

  • Support multimedia - so that users can share animations and videos. this is important to provide an experience to users that makes the project appraling. there is progress made on the ui component library to provide various features and functionality users expect in a messaging app.

  • Minimize metadata - so no one knows who’s messaging who or when. i think the metadata is faily minimal, but ultimately is reletive to how feature-rich i want the application. things like notification that a "user is typing" can be disabled, but its a common offering in normal messaging apps. similarly i things read-reciepts can be a useful feature but comes with metadata overhead. i hope to discuss these feature more in the future and ultimately provide the ability to disable this.

Orange

  • Open source - moving towards a hybrid approach where relevent repositories are open source.

  • Remove registration - creating a messaging app that eliminates the need for users to register is a feature that i think is desired in the cybersec space. the webapp approach seems to offer the capabilities and is working. as i move towards trying to figure out monetization, im unable to see how registration can be avoided.

  • Encrypted storage - browser based cryptography is fairly capable and its possible to have important data like encryption keys encrypted at rest. this is working well when using passkeys to derive a password. this approach is still not complete because there will be improvements to take advantage of the filesystem API in order to have better persistence. passkeys wont be able to address this easily because they get cleared when you clear the site-data (and you lose the password for decrypting the data).

  • User education - the app is faily technical and i could use a lot more time to provide better information to users. the current website has a lot of technical details... but i think its a mess if you want to find information. this needs to be improved.

  • Offline messaging - p2p messaging has its limitations, but i have an idea in mind for addressing this, by being able to spin up a selfhosted version that will remain online and proxy messages to users when they come online. this is still in the early stages of development and is yet to be demonstrated.

  • Self-destructing messages - this is a common offering from secure messaging apps. it should be relatively simple to provide and will be added as a feature "soon".

  • Javascript - there is a lot of rhetiric against using javascript for a project like this because of conerns about it being served over the internet. this is undestandable, but i think concerns can be mitigated. i can provide a selfhostable static-bundle to avoid fetching statics from the intetnet. there is additional investigation towards using service workers to cache the nessesary files for offline. i would like to make an explicit button to "fetch latests statics". the functionality is working, but more nees to be done before rolling out this functionality.

  • Decentralized profile: users will want to be able to continue conversations across devices with multidevice-sync. It's possible to implement a p2p solution for this. This is an ongoing investigation.

  • STUN/TURN servers - the app is using the metered.ca turn servers only for brokering p2p connections. you have the option to use your own api key to do things like enable a “relay-mode”, which will proxy all messages. im open to make this as configurable as nessesary if users want to add multiple of their own servers.

Red

  • Regular security audits - this could be important so that vulnerabilities can be identified and fixed promptly. security audits are very expensive and until there is any funding, this wont be possible. a spicier alternative here is an in-house security audit. i have made attempts to create such audits for the signal protocols and MLS. im sure i can dive into more details, but ultimately an in-house audit in invalidated by any bias i might impart.

  • Anonymity - so that users can communicate without revealing their identity is a feature many privacy-advocates want. p2p messages has nuanced trandoffs. id like to further investigate onion style routing, so that the origins can be hidden, but i also notice that webrtc is generally discourage when using the TOR network. it could help if users user a VPN, but that strays further from what i can offer as part of my app. this is an ongoing investigation.

Demo

FAQs:

Why are there closed source parts? - This project comes in 2 flavours; open-source and close-source. To view the open source version see here. ive tried several grants applications and places that provide funding for open source project. im aware they exist… unfortunately they rejected this project for funding. Im sure many are inundated with project submissions that have a more professional quality and able to articulate details better than myself. Continuing with open source only seems to put me at a competative disadvantage.

Monetization - Im investigating introducing clerk. I hope to use that to create a subscription model. I would like to charge $1 per-month as per the minimum allowed by clerk. I started off thinking i could avoid charging users entirely given it seems a norm for secure messaging apps to be free. but given the grant rejects and the lack of donations on github sponsors (completely understandable), but its clear that it wont be able to sustain the project. I tried Google adsense on the website/blog but it was making practically nothing; so i disabled it because it wasnt a good look when it goes against the whole “degoogling” angle. This project is currently not funded or monnetized in any way. (Its not for lack of trying)

How does it compare against signal, simpleX, element, etc? - The project is far from finished and it woudnt make sense to create something as clear as a comparison table. Especially because core features like group-messaging isnt working. Some technical details can be seen here if your want to draw your own comparison.

Javascript over the internet is not secure - im investigating the to use service workers to cache the file. this is working to some degree, but needs improvement before i fully roll it out… i would like to aim for something like a button on the UI called “Update” that would invalidate the service-worker cache to trigger an update. I hope to have something more elegant than selfhosting on localhost or using a dedicated app. its possible to provide a static bundle that can work from running index.html in a browser without the need to run a static server. The static bundle of the open source version can be seen and tested to work from this directory: https://github.com/positive-intentions/chat/tree/staging/Frontend . When i reach a reasonable level of stability on the app, i would like to investigate things like a dedicated app as is possible on the open source version. https://positive-intentions.com/blog/docker-ios-android-desktop

How is this different to any other messaging app? - the key distinction between this project and other like it like signal and simpleX is that its presented as a PWA. A key cybersecurity feature of this form-factor is that it can avoid installation and registration. its understandable that such a feature doesnt appeal to everyone, but along with the native build, it should cover all bases depending on your threat model.

What about Chat Control? - I see a lot a fear mongering in the cybersecurity community around chat-control. I aim to create something that doesn't have the censorship pitfalls of a traditional architecture. A previous post on the matter: https://www.reddit.com/r/europrivacy/comments/1ndbkxn/help_me_understand_if_chatcontrol_could_affect_my

Is it vibecoded? - AI is being used appropriately to help me in various aspects. I hope it doesnt undermine the time and effort i put into the project.

Aiming to provide industry grade security encapsulated into a standalone webapp. Feel free to reach out for clarity on any details or check out the following links:

IMPORTANT NOTE: It's worth repeating, this is still a work in progress and not ready to replace any existing solution. many core features like group-messaging are not working. Provided for testing, demo and feedback purposes only.


r/positive_intentions • • Nov 22 '25

P2P Instant Messenger

3 Upvotes

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!

Check out the pre-release demo here.

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


r/positive_intentions • • Oct 07 '25

No-hassle P2P Calls in an Browser

3 Upvotes

Want encrypted WebRTC video calls with no downloads, no sign-ups, and no tracking?

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

Check out the demo: P2P Calls


r/positive_intentions • • Feb 24 '25

Looking for people to register as testers for my app.

Thumbnail
reddit.com
3 Upvotes

r/positive_intentions • • Feb 01 '25

Introducing Decentralized File Transfer

3 Upvotes

r/positive_intentions • • Jan 15 '25

Selfhosted P2P File Transfer & Messaging PWA

3 Upvotes

App: https://chat.positive-intentions.com/

A p2p encrypted file transfer and messaging app. Here are some features below:

  • Open Source

  • Cross platform

    • PWA

    • iOS, Android, Desktop (self compile)

    • App store, Play store (coming soon)

    • Desktop

      • Windows, Macos, Linux (self compile)

      • run index.html on any modern browser

    • Decentralized

  • Secure

    • No cookies

    • P2P encrypted

    • No registration

    • No installing

  • Messaging

    • Group Messaging (coming soon)

    • Text Messaging

    • Multimedia Messaging

    • Screensharing (on desktop browsers)

    • Offline Messaging (in research phase)

    • File Transfer

    • Video Calls

  • Data Ownership

    • Self Hosting

    • GitHub pages Hosting

    • Local-Only storage

Check it out!


r/positive_intentions • • Sep 19 '24

Dim: Functional Web Components

Thumbnail
positive-intentions.com
3 Upvotes

r/positive_intentions • • Sep 02 '24

The Official positive-intentions Blog

Thumbnail
positive-intentions.com
3 Upvotes

r/positive_intentions • • May 31 '24

Decentralized Computer

3 Upvotes

https://chat.positive-intentions.com/#/desk

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

Webtops offer the promise of a desktop-like experience within a web browser, making it possible to run applications and manage files without needing traditional operating systems. This innovation can transform how we can use devices, making them more versatile and accessible. One notable implementation is Puter, which provides a kind of cloud operating system by storing data on a backend server. This approach ensures that user data is accessible from any device, enhancing the user experience significantly.

The Challenge of user adoption

One of the primary issues with current webtop implementations is data storage. Many webtops rely on browser storage, which can be limited in capacity but also prone to data loss if the browser's cache is cleared or if the user switches devices. While backend storage solutions like those employed by Puter mitigate this issue, they come with their own set of challenges, including dependency on server availability and potential privacy concerns.

Exploring P2P Technology for Webtops

An alternative approach to backend storage is leveraging P2P technology to share the filesystem between different devices. This method could decentralize data storage, reducing reliance on a central server and potentially enhancing data security and availability. By using P2P networks, each device in the network can share and synchronize files, creating a robust and resilient storage solution.

Investigating DaedalOS

In our exploration of webtop environments, we have investigated various options and are particularly interested in DaedalOS. This integrated webtop environment shows promise in terms of features and capabilities. However, like many early-stage technologies, it comes with integration challenges. The complexity of integrating DaedalOS into existing applications without sufficient documentation is a significant hurdle that needs addressing.

Puter

Puter stands out as a great implementation of a webtop, boasting extensive features, capabilities, and support. However, its integration into our application has proven to be prohibitively complicated at this early stage of our investigation. The lack of detailed documentation and support materials makes it difficult to fully leverage its potential within our app.

The plan

  1. Introduce a webtop OS into the app (done)

  2. Update storage funtionality to use our blockchain solution

  3. Introduce real-time filesystem sync.

  4. Introduce webpack module federation to better integrate into the app

  5. ???

  6. Users get a decentralized selfhosted operating system as a PWA

Conclusion

Webtops represent a fascinating evolution in computing, offering the potential to transform our interaction with devices and applications. However, significant challenges remain, particularly in the areas of data storage and integration. Exploring alternative solutions like P2P technology for file system sharing could provide a viable path forward. As we continue to investigate and develop these technologies, the key to their success will be in overcoming these obstacles and making the integration process more accessible and straightforward.

We are keen to hear your thoughts on these issues. Have you encountered similar challenges with webtops? What solutions have you found effective? Let's continue the conversation and work towards making webtops a practical and powerful tool for all users.


r/positive_intentions • • May 09 '24

First Medium Article

Thumbnail
medium.com
3 Upvotes

r/positive_intentions • • Apr 05 '24

[Open Source] P2P Whatsapp, Instagram and Metaverse as a PWA

3 Upvotes

Hello everyone,

chat.positive-intentions.com

I'm thrilled to announce that I am open-sourcing my project, a decentralized chat application designed as a Progressive Web App (PWA) built entirely in JavaScript. This decision marks a significant step forward for the project, aiming to embrace the ethos of transparency, collaboration and community feedback.

For those who might not have seen my previous posts, here's a brief rundown of what this app brings to the table:

  • Secure Messaging: Utilizing end-to-end encryption to ensure that your messages remain private and secure.

  • File Sharing: Leverage WebRTC technology and QR codes for easy and secure file transfers.

  • Voice and Video Calls: Connect with friends, family, or colleagues through seamless voice and video calls.

  • Shared Virtual Space: Explore a shared mixed-reality space, offering an experience akin to entering a metaverse.

  • Image Board: An intuitive, scrollable format for browsing and sharing images, inspired by platforms like Instagram.

You can find a high-level overview of the app’s workings here and some initial thoughts and features discussed in this post.

Initially, I was exploring various avenues for monetization but found it challenging to settle on an approach. This exploration has led me to consider GitHub Sponsors as a potential means to fund further development. I’m open to other ideas and would love to hear your thoughts.

Previously, I was cautious about a "big-bang" open-sourcing approach, as outlined here. However, I've decided that open-sourcing the project now is the best path forward. It will allow me to engage more deeply with the community on the app's security and privacy features—areas I’ve claimed to excel in, but have rightly been critiqued for not being verifiable in a closed-source model.

I acknowledge the importance of good documentation in open-source projects. However, I must admit that the documentation for this project is not yet comprehensive. The codebase remains a work-in-progress and it is far from being a complete proof-of-concept. It might present challenges in understanding. For now, the best form of documentation might just be the code itself, alongside discussions on our subreddit: r/positive_intentions. Your questions and curiosity are welcome.

What Open-Sourcing the Project Aims to Achieve:

  • Enhanced Feedback: Open-sourcing allows me to gather invaluable feedback from the community, helping refine and improve the app.

  • Focus on Security and Privacy: It opens the door for more in-depth analysis and contributions toward the app’s security and privacy capabilities.

  • Support through GitHub Stars and Sponsors: If you believe in the project, your stars on GitHub and potential sponsorship can provide much-needed support.

This journey is just beginning and I'm excited to see where collaborative development can take this project. Thank you for your interest, support and feedback.


r/positive_intentions • • Dec 01 '23

Introducing Decentralized P2P Location Sharing

3 Upvotes

In our decentralized p2p chat app, we would like to introduce location sharing.

Location sharing is a feature seen in many chat apps and so we investigated options to intoduce it into our app to align to functionalities provided by mainstream chat apps.

Our app is purely browser based and if the user grants the browser permissions for GPS data, this can be easily shared with a peer.

GPS data alone is pretty useless unless we can also display it on a map. So we are also introducing openstreetmap and leaflet.js to display the information.

While the data from openstreetmap.org is not inherently decentralized, it is possible to self-host for those who are able to. The app does not support selfhosted maps at the moment, but we will be looking to introducing such functionality in the future to align to the decentralization philosophy of the app.

About the app:

It is a chat app in javascript that runs on a browser. It is a work-in-progress and a proof-of-concept to see if its possible to create chat app in javascript without putting any dependency on a server for authentication+encryption. Some core functionality is working, but there is much to do on the app. There are many limitations in creating an app like this and its important to note, this is an investigation of "if" and "what" is possible in a P2P architecture to see if we can create decentralized functionality of mainstream alternatives. The app is in early development and provided as a demo. it isnt intended to replace mainstream alternatives.

Check out the app here: positive-intentions

We'd like to hear what you think of the progress so far and are open to feature requests.


r/positive_intentions • • Oct 25 '23

Decentralizing Social Media: Your Thoughts?

3 Upvotes

Hey everyone!

I wanted to reach out to the community to get your input on something we're considering for our decentralization app.

As some of you may already know, our app is a bit unique. While there are apps out there with similar functionality in "what it does", we dont believe there is an implementation similar to our app in "how it works". The app has been steadily evolving with a focus on secure and efficient communication. We've introduced features like text messaging, audio/video calls, screensharing (on desktop browsers) and robust authentication/encryption, all designed to provide you with a secure and seamless chat experience.

As a proof-of-concept app, we're now thinking to round-off development on the chat functionality and introduce social media functionality to our app.

This mode is more than just a photo-sharing feature. It's part of our larger mission to explore options for decentralization. We understand the limitations of our app, which means there won't be a "global feed" like traditional social media platforms. Instead, the content you see will be composed of media shared by your peers within shared contexts we're calling "pods".

Now, here's where we hope it gets interesting for the tech savvy: We're using blockchain technology for message management, but it's not the same as what you'd find in a global blockchain like Ethereum. Our blockchain implementation is entirely JavaScript-based, running in your browser and it's designed for communication within these pods, not on a global scale. It's a lightweight, secure way to manage messages, ensuring that your content remains within the shared context you intend.

We're putting together a mock UI demo with fake data (which will likely be updated since this post) to give you a glimpse of how it might look and function. It's important to note that this social media mode isn't intended to replace any other platform. Instead, it's an experiment to see if we can create a decentralized social media experience with a reasonable amount of functionality.

Here's where we need your help:

  1. What do you think about the idea of decentralizing social media within our app?

  2. How do you envision this Instagram-like mode working within the "pods" context?

  3. Are there any features or functionalities you'd like to suggest for this mode?

  4. Do you know of any other projects or platforms exploring similar decentralized social media concepts?

We have been using feedback from Reddit to guide the app development. Your feedback is incredibly valuable to us and it will play a pivotal role in shaping the direction of this experiment. We've always been committed to making our app as user-centric as possible and your input helps us achieve that goal.

Feel free to share your thoughts, ideas, or any suggestions you may have regarding this endeavor. Your feedback fuels our progress and we can't wait to hear what you think!

Thanks for reading.

Check out the social media UI demo here.


r/positive_intentions • • Oct 14 '23

POC: Decentralized P2P Secure File Transfer

3 Upvotes

While there are numerous chat apps out there, we've taken a unique approach to the problem, starting with the fundamental aspect of "chat functionality."

In our decentralized ecosystem, we're excited to introduce the capability for file transfers. Thanks to our use of PeerJS and WebRTC technology, file transfers are not only secure but incredibly efficient. Imagine a scenario where you need to send a file to another device without relying on traditional cloud storage providers—our app is designed for exactly that purpose.

It's essential to note that this feature is a work in progress, but it's now available for testing.

Our app also offers several other features, including:

  • Text messaging

  • Audio and video calls

  • Desktop screensharing

  • Robust authentication and encryption

  • Group chat

If you're interested in exploring these features and witnessing the future of decentralized chat, check out our app here.

Stay tuned for more exciting updates as we continue to enhance your chat experience!


r/positive_intentions • • Oct 07 '23

🐋 positive-intentions: Decentralized Chat.

3 Upvotes

Id like to introduce a decentralised chat app: positive-intentions.

A decentralized infrastructure has many unique challenges. Ive taken feedback from previous posts and have made updates. Its still a work-in-progress, but it's testable and it would be great if you can tell me what you think.

Some of the features of the app include:

  • Free

  • Decentralised

  • No cookies

  • P2P encrypted

  • No registration

  • No installing

  • Group messaging

  • Text messaging

  • Multimedia messaging

  • Offline messaging (related post)

  • File transfer (coming soon)

  • Video calls

  • Data-ownership

  • Selfhosted (optional)

  • Screensharing (on desktop browsers)

  • OS notifications (where supported)

With no registration or installation required, its easy to get started on our decentralized chat app!


r/positive_intentions • • Oct 07 '23

A Chat App For Bad Internet Connections.

3 Upvotes

We all know the struggle of dealing with slow or unreliable internet connections. Whether you're in a remote location, using a crowded Wi-Fi network, or facing other connectivity challenges, it can be incredibly frustrating when your chat app just won't cooperate. But fear not, because our app is here to save the day!

Why is Our App Lightning Fast?

The secret to our app's speed lies in its clever use of technology, particularly PeerJS and WebRTC. But what are these mysterious acronyms, and how do they work their magic? Let's break it down in simple terms.

PeerJS: Imagine our app as a digital walkie-talkie. Instead of relying on a central server, like many traditional chat apps, we use PeerJS to establish direct connections between your device and your chat partner's device. This direct connection is like having a private line for your conversation, cutting out the middleman (the server) and reducing delays.

WebRTC: Think of WebRTC (Web Real-Time Communication) as the engine that powers our speedy conversations. It's a technology built into web browsers that allows real-time audio, video, and data sharing without the need for plugins or external software. With WebRTC, your messages travel directly from your device to your chat partner's device, taking the shortest and quickest route possible.

Why Our App Shines in Bad Internet Conditions:

Now, let's talk about why our app excels in less-than-ideal internet conditions:

  1. Reduced Reliance on Servers: Unlike many chat apps that heavily depend on central servers, we minimize server involvement. This means that even if your internet connection is sluggish, you can still send and receive messages without waiting for a server to process your data.

  2. Efficient Data Transfer: Peer-to-peer connections are incredibly efficient when it comes to data transfer. We only send the data necessary for your conversation, cutting down on unnecessary overhead. This efficiency makes our app work smoothly even on slower connections.

  3. Local Area Network (LAN) Benefits: If you're chatting with someone on the same local network (like in an office or at home), our app recognizes this and sets up a direct LAN connection. LAN connections are super fast because they don't rely on external internet infrastructure.

  4. Adaptive Bitrate: Our app dynamically adjusts the quality of audio and video streams based on your current internet conditions. This means that even if your connection is choppy, you can still have a clear conversation without constant interruptions.

So, whether you're chatting with a friend from halfway around the world or talking to a colleague in the same office, our app's focus on direct peer-to-peer communication, efficient data transfer, and adaptive technology ensures that your messages get through quickly and reliably, even in challenging internet environments.

Stay connected, no matter where you are, with our lightning-fast chat app!

Happy chatting! 🚀


r/positive_intentions • • Feb 06 '26

Introducing Quantum-Resistant Encryption

2 Upvotes

r/positive_intentions • • Jul 21 '25

Decentralized Module Federation For A Microfrontend Architecture

2 Upvotes

While it could be considered overly complicated (because, well, it is), I'm trying something new, and it's entirely possible this strategy won't be viable long-term. My philosophy is "there's only one way to find out." I'm not necessarily recommending this approach, just sharing my journey and what I'm doing.

Architectural Overview

Here's how I'm architecting it:

Potential Benefits

I've identified some interesting benefits to this approach:

While I often see module federation and microfrontends discouraged in online discussions, I believe they're a good fit for my specific approach. I'm optimistic about the benefits and wanted to share the details.

When serving the federated modules, I can also host the Storybook statics. I think this could be an excellent way to document the modules in isolation.

Modules and Applications

Here are some examples of the modules and how they're being used:

This setup allows me to create microfrontends that consume these modules, enabling me to share functionality between different applications. The following applications, which have distinct codebases (and a distinction between open and closed source), would be able to leverage this:

Sharing these dependencies should make it easier to roll out updates to core mechanics across these diverse applications.

Furthermore, this functionality also works when I create an Android build with Tauri. This could streamline the process of creating new applications that utilize these established modules.

Considerations and Future

I'm sure there will be some distinct testing and maintenance overhead with this architecture. However, depending on how it's implemented, I believe it could work and make it easier to improve upon the current functionality.

It's important to note that everything about this project is far from finished. Some might view this as an overly complicated way to achieve what npm already does. However, I think this approach offers greater flexibility by allowing for the separation of open and closed-source code for the web. Of course, being JavaScript, the "source code" will always be accessible, especially in the age of AI where reverse-engineering is more possible than ever before.