/r/darknetplan
This subreddit is dedicated to organizing a decentralized alternative to traditional ISP's.
New to /r/DarknetPlan & Hyperboria?
Find your Meshlocal & check out the docs!
Other things to check out include:
Please do not post the following:
Funny pictures
Links to items for sale or to a promo page for a product or item. (Discussions of a product or item are fine)
Promotion of job openings
Unrelated projects (ie. tor) or topics (ie. piracy). This is for discussion of Hyperboria, not tor, not i2p, not where to get the latest blockbuster for free. /r/tor exists for a reason, as does /r/privacy, /r/torrents, etc. Check out this post for a nice list.
Suggestions to use ham, CB, terahertz, ELF, quantum, akashic field, or FRS radios for a mesh network. For more information, search the subreddit for past posts on these subjects.
Posts may be removed at the moderator's discretion. Removed posts will be in /r/Uncensorship
Please message the mods to have your meetup added here
Meshnet Related Subreddits:
/m/Meshlocals - Aggregates 70+ subreddits!
Terminology, just to clear up a few misconceptions:
Darknet: An anonymizing overlay network, usually running over the internet. Examples: Tor, i2p, freenet.
Meshnet: A decentralized peer-to-peer network, with user-controlled physical links. Usually wireless. Examples: Seattle Wireless, Wireless.org.au.
Clearnet: The Internet at large, or any network which has no inherent cryptographic security, authenticity, or anonymity. Examples: internet, unencrypted meshnets.
The Meshnet: Used here, "the meshnet" refers the transitional CJDNS internet overlay network currently known as Hyperboria.
/r/darknetplan: A place to organize efforts to create a hardware/software stack for a globally scalable system of interconnected local meshnets. We realize that the inclusion of "darknet" in this name does not properly describe our current objectives, but the meshnet is a necessary foundation for the final goal of a truly resilient darknet.
Thanks to bepraaa for getting these definitions in order
Anything we missed? Message us mods & we'll gladly fix it.
/r/darknetplan
I was provoticting some vendors with my methods to set a trap. Now i have so many evidences who vendor is.experience from 15 years old
i recently heard of CJDNS and i am setting the app up but idk if Theres any england users so i can connect to england Cjdns mesh network of it so i can browse the hyperboria any tips?
Meshtastic is getting a lot of ground on YouTube, but I was wondering if there are any open sources radio mesh projects that are in the works.
Both for radio communication and drone/robot control something to send data telemetry.
Hello All,
We’re excited to invite you to a special online event on September 12th at 4 PM UTC! 🚀
Dasharo User Group (DUG) is your go-to forum for Dasharo enthusiasts—whether you’re a seasoned user or just curious! This is your chance to dive deep into the latest developments, new features, and exciting updates in the Dasharo ecosystem. It’s the perfect opportunity to connect, share knowledge, and learn about new features and updates that are coming to Dasharo.💡
But that’s not all! We’ll also be hosting vPub 0xC, a more laid-back, open-format session where the conversation flows freely. Grab your favourite beverage 🍻, and join in as we chat about anything and everything related to open-source firmware and hardware.
Expect some fascinating talks from industry experts: Regalis, Philipp Deppenwiese from Binarly, Stuart Yoder from Arm, and last but not least, Michał Żygowski from 3mdeb, who will present an exciting demo of Dasharo on Odroid H4+! There will also be plenty of time for an open, relaxed discussion where everyone can contribute. 🙌
Mark your calendars—you won’t want to miss it! ✨
Join links & full schedule are available here:
https://vpub.dasharo.com/e/14/dasharo-user-group-7
Register for free at:
https://vpub.dasharo.com/e/14/dasharo-user-group-7/#tickets
Demo video: https://www.youtube.com/watch?v=npmnME8KdQY
To further enhance the security offerings of our app, we would like to introduce a way to validate a peer's public key. This could help protect against MITM or other compromises on encryption keys.
How it works:
Future enhacements:
About the app:
Just curious to anyone’s favorite browser to use on iPhone for various purposes!
Who ever is interested in learning darkweb join r/darknet_questions
I will buy a new laptop soon. I want it as anonymous as possible. Tips?
Hello, I'm interested in the darknet but have no plan how to get in there so. Of course I know that you need the tor and an onion link but how do I find it and yes I want to get really deep in I don't just want to scratch the surface can someone help me?
To avoid missing out future events, join our tiny-volume event notification newsletter (no spam, just ~4 e-mails per year)
Dear Friends, I invite you to a joint "DUG#6 & vPub 0xB" event that starts 13th June at 4 PM UTC :
Join links & full schedule are available here:
DUG#6 & vPub 0xB opensource online Party!
Hi. So this may feel like a dumb and most frequently asked question. But what are some other alternatives to Tor for mobile to access the dark web? Am asking because I have searched everywhere and can't seem to find anything. The problem with Tor is slow . Are there any better alternatives to Tor mobile?
Does anyone know if To 2 Door is still available market place? Last I used it was in august when you had to pay to get the url so it didn’t get hacked. But when I went to DNM.watch I didn’t see anything. Any suggestions cause the vendor I used on there was always on point and very reliable. (Platinumxanax)
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.
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.
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.
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 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
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.
So no issues accessing the darknet but once there I am totally lost! Can anyone advise how I access marketplaces as I discovered you can't just put a search in? 🤔
Decentralization can mean a lot of things because it can be open to interpretation. In this article, we would like to talk about what decentralization means to us and how we are approaching our definition of decentralized. We are working on a typical chat app, but our approach is unique and may push the boundaries of what it means for something to be self-hosted.
Our decentralized chat application is built as a Progressive Web Apps (PWA) and leverages modern web technologies to deliver a user experience comparable to native apps. Unlike traditional centralized chat apps, our chat app is designed to operate independently of central servers, ensuring that user data remains private and secure. This article will delve into the various components and architectural decisions that make our app truly decentralized.
An overview of how our chat application leverages Progressive Web App (PWA) technology to provide a seamless user experience across different devices and platforms.
A typical app relies heavily on data storage and networking capabilities. In our decentralized chat application, we’ve implemented advanced solutions to handle these aspects efficiently and securely.
In our app, we use IndexedDB to store data directly in the browser’s storage. While browsers provide multiple options for storing information, ranging from cookies to local storage, IndexedDB offers a more advanced and robust solution.
Capacity: IndexedDB can store significantly larger amounts of data compared to cookies or local storage.
Structure: It allows for complex data structures, including collections of files and blobs.
Performance: IndexedDB operates asynchronously, meaning it won’t block the main thread of your application, leading to better performance for data-heavy applications.
Using IndexedDB, we ensure that user data is stored locally on their devices, providing both privacy and independence from central servers.
For networking, our app uses PeerJS-server as a connection broker to establish WebRTC connections between peers.
Direct Peer-to-Peer: WebRTC, provided by the browser, enables real-time communication between peers. This allows two users to connect directly and exchange data with minimal latency.
Efficient Routing: Once a connection is established, data is sent via the shortest possible network route, enhancing speed and efficiency.
Multiple Connections: Browsers can handle multiple WebRTC connections simultaneously, though the number of connections can vary depending on the device and network capabilities.
PeerJS-server helps in the initial connection setup by acting as a signaling server. It facilitates the exchange of connection information between peers, enabling them to establish a direct WebRTC connection.
By leveraging IndexedDB for data storage and WebRTC with PeerJS-server for networking, our chat application achieves a high level of decentralization, ensuring user data remains private and connections are efficient and reliable. These components form the backbone of our approach, pushing the boundaries of what it means for an app to be truly self-hosted and decentralized
Our app is essentially a bundle of static files, which makes it highly portable and easy to distribute. We leverage AWS services such as S3 and CloudFormation to deploy our app, ensuring it is distributed efficiently over a Content Delivery Network (CDN) across AWS servers.
AWS S3: We host our app on AWS S3, a scalable storage service that allows us to serve static files reliably. S3 ensures that our app is always available and can handle large numbers of requests without performance degradation.
CloudFormation: By using AWS CloudFormation, we automate the deployment process, managing our infrastructure as code. This makes it easy to replicate and manage our app’s deployment environment.
Hosting on S3 and using CloudFormation means our app benefits from AWS’s global CDN. This ensures that our static files are cached and served from servers closest to our users, reducing latency and improving load times.
We go a step further by providing users with the option to download a zip file of the app directly from within the app. This ensures that users can run the app locally without relying on our servers.
Direct from Index.html: Unlike some other apps, our app is a pure JavaScript implementation, designed to run directly from the index.html file. Users can simply open this file in their browser and start using the app without needing a server.
Docker Option: For users who prefer or require a server setup, we offer a Docker configuration. This allows the app to be run in a containerized environment, providing flexibility and ease of deployment for different use cases.
We believe in transparency and accessibility. Therefore, we run the app as unminified code. This has several advantages:
Ease of Download: Users can download the entire app using simple browser commands like Ctrl/Cmd+S.
Transparency: By providing unminified code, we ensure that users can inspect and understand the code they are running. This fosters trust and allows for easier customization and debugging.
By distributing our app as static files and offering multiple ways to run it, we ensure that users have maximum flexibility and control. Whether using AWS’s robust infrastructure or running the app locally, our approach embodies the principles of decentralization and user empowerment.
Our app leverages Webpack 5’s Module Federation feature to implement a microfrontend architecture. This approach allows us to modularize our application, making it easier to maintain, develop, and scale. You can explore our open-source implementation here: https://github.com/positive-intentions/frontend-base.
We have used Webpack 5 Module Federation to build the chat application, which you can find here: https://github.com/positive-intentions/chat. Additionally, we have created a federated module for cryptography that can be imported at runtime, available here: https://github.com/positive-intentions/cryptography. Our current setup is straightforward, allowing us to dynamically load different parts of the application as needed. This modular approach provides flexibility and efficiency in how we develop and deploy our app.
We plan to further decompose the application into separate microfrontends, each responsible for a specific aspect of the app. This will not only simplify maintenance but also enhance documentation and development processes for individual components.
Planned Modules:
1. UI Components: A collection of reusable UI components that can be shared across different parts of the application, promoting consistency and reducing duplication.
2. P2P Framework: The core framework for peer-to-peer networking, facilitating real-time communication between users.
3. State Management: This module will manage the application’s state, ensuring efficient data handling and synchronization across different components and peers.
4. Permission Manager: A dedicated module for managing user permissions and access control, enhancing security and user management.
Each module will have its own Storybook and module export, providing a dedicated space for documentation, testing, and showcasing individual components. This approach will:
Enhance Documentation: Each module will be well-documented, making it easier for developers to understand and use them.
Simplify Maintenance: By isolating modules, we can update and maintain them independently, reducing the risk of breaking changes affecting the entire app.
Promote Reusability: Well-defined modules can be reused across different projects, promoting a modular and efficient development approach.
By embracing Webpack 5 Module Federation and breaking down our app into distinct microfrontends, we aim to create a more robust, scalable, and maintainable architecture. This approach not only benefits our development process but also enhances the overall user experience by ensuring that each component is well-crafted and easily accessible.
In the past, we have encountered difficulties when deploying our app to AWS due to various technical issues. Given that our app functions as a self-hosted static application, we have started exploring alternative hosting options, such as GitHub Pages. You can view our deployment on GitHub Pages here: https://positive-intentions.github.io/chat.
Our microfrontend architecture allows us to deploy each module independently. This capability has enabled us to host copies of the app on GitHub Pages for each repository. While this approach is unconventional and can lead to redundant copies of the app, we believe it is a valuable exercise in exploring module federation redundancy.
Accessibility: Hosting on GitHub Pages makes the app easily accessible to users and developers.
Simplicity: GitHub Pages offers a straightforward deployment process, reducing the complexity often associated with other hosting solutions.
Cost-Effective: GitHub Pages is free, making it an economical choice for hosting static sites.
We aim to make our app interoperable across different hosting sources. By leveraging Webpack 5 Module Federation, we can ensure that the app works seamlessly whether it is served from AWS or GitHub Pages. This redundancy enhances the app’s reliability and availability.
Module Federation Redundancy: We are investigating ways to make modules interoperable between different sources, ensuring that the app remains functional even if one source becomes unavailable.
Interoperable Deployment: Our goal is to allow the app to fetch and integrate modules from both AWS and GitHub Pages dynamically.
To further enhance our deployment strategy, we plan to use a infrastructure as code tool, to deploy the app across multiple cloud service providers. This approach will increase the resilience of our deployment, ensuring the app remains online and functional even if one provider experiences downtime.
Multi-Cloud Deployment: We can deploy the app to various cloud service providers, including AWS, Azure, and Google Cloud. This will distribute the app’s load and reduce the risk of a single point of failure.
Scalability: This will enable us to scale the app easily across different providers, ensuring it can handle increased traffic without performance issues.
Cost Management: Static file hosting is relatively a cheap option for hosting a webapp, we can optimize costs and ensure that the app remains affordable to maintain.
By exploring these new hosting options and implementing a robust deployment strategy, we aim to make our decentralized chat app more resilient, scalable, and cost-effective. Our efforts in redundancy and interoperability will ensure that the app continues to function seamlessly, providing a reliable user experience regardless of the hosting source.
As our app continues to develop, we are excited to introduce the concept of a decentralized profile that can be shared across multiple devices. This feature is designed for individuals who want to use the same profile on all their devices, providing a seamless and integrated multi-platform chat experience, much like any modern chat application.
A decentralized profile allows users to maintain a consistent identity and settings across different devices. This means that whether you are using a smartphone, tablet, or desktop, your profile can remain synchronized and up-to-date.
Profile Synchronization: Users can access their chat history, contacts, and settings on any device by synchronizing their decentralized profile.
Data Consistency: Changes made on one device are automatically reflected on others, ensuring a consistent experience.
Implementing a decentralized profile enables us to offer a robust multi-platform chat experience. Users can switch between devices without losing their chat continuity or settings, enhancing the overall user experience.
Convenience: Users can start a conversation on one device and continue it on another without any interruptions.
Flexibility: The app adapts to various devices, providing a user-friendly interface and experience on each platform.
In addition to profile synchronization, we are exploring the potential of decentralized file storage. This feature would allow users to move large files between devices quickly, easily and securely.
Cross-Device Sharing: Users can share files between their devices effortlessly, whether they are transferring a document from their laptop to their phone or vice versa.
Collaborative Work: Teams can collaborate more effectively by sharing encrypted files directly through the app, regardless of the devices they are using.
By introducing a decentralized profile and exploring decentralized file storage, we aim to enhance our app’s functionality and user experience. These features will provide users with the convenience and flexibility expected from a modern chat application while maintaining the principles of decentralization and security.
Decentralized peer discovery is a critical component of our app’s architecture. By leveraging innovative technologies such as QR codes, NFC, and BLE, we facilitate seamless connections between peers without relying on a central authority.
QR codes provide a straightforward method for establishing peer connections. Users can generate a QR code that contains their connection details, which other users can scan to initiate a peer-to-peer connection.
Ease of Use: Users can quickly and easily share connection details.
Security: QR codes can be generated dynamically, reducing the risk of interception.
NFC allows devices to establish connections simply by being in close proximity. This technology is particularly useful for quick and secure peer discovery.
Speed: Connections are established almost instantly.
Convenience: Users can connect devices by simply bringing them close together, making it ideal for spontaneous interactions.
BLE enables devices to discover and communicate with each other over short distances with minimal power consumption. This makes it a suitable option for maintaining constant peer-to-peer connections.
Energy Efficiency: BLE conserves battery life, making it ideal for mobile devices.
Range: BLE provides a reliable connection over a short range, perfect for personal or localized networking.
By integrating QR codes, NFC, and BLE, we create a robust and versatile peer discovery mechanism. Users can choose the most convenient method for their situation, ensuring that connections are both seamless and secure.
Hybrid Approach: Users can combine different methods for an optimal connection experience. For instance, initial discovery via QR code followed by connection via BLE for sustained communication.
Adaptability: The app adapts to the available technologies on the user’s device, providing the best possible peer discovery experience.
These innovative approaches to peer discovery, coupled with our decentralized microfrontend architecture, form the backbone of our commitment to enhancing decentralization, scalability, and user experience. By continually exploring and implementing cutting-edge technologies, we ensure our app remains at the forefront of decentralized communication solutions
These sections outline the key aspects of our decentralized microfrontend architecture and provide a roadmap for our ongoing and future efforts to enhance decentralization, scalability, and user experience.
Our journey towards building a decentralized chat application has been driven by a desire to push the boundaries of what it means for an app to be truly self-hosted and independent of central servers. By leveraging modern web technologies such as Progressive Web Apps, IndexedDB, WebRTC, and Webpack 5 Module Federation, we have created a robust and scalable architecture that emphasizes privacy, security, and user empowerment.
We have explored innovative hosting solutions like GitHub Pages and plan to implement multi-cloud deployments to enhance resilience and scalability. Our vision for a multi-device architecture, incorporating decentralized profiles and encrypted file storage, aims to provide a seamless, cross-platform user experience. Additionally, our commitment to decentralized peer discovery using QR codes, NFC, and BLE ensures that users can connect easily and securely without relying on centralized authorities.
As we continue to develop and refine our app, we remain dedicated to the principles of decentralization, transparency, and user control. We invite you to join us on this journey, explore our open-source repositories, and contribute to the ongoing evolution of our decentralized chat application. Together, we can redefine what it means to communicate in a decentralized world.
Thank you for taking the time to read about our project. We look forward to your feedback and collaboration as we continue to innovate and improve our decentralized chat application.
Hello everyone,
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:
You can find a high-level overview of the app’s workings here and some initial thoughts and features discussed in this post. An easy way to test out the app is between two of your devices like a phone and laptop.
The app is working in a unique way in how it stores large amounts of files in the browser (indexedDB) so the storage used is always on your local device, but has a couple other selhosting options:
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:
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.
I am a Russian man who escaped from Russia and was granted asylum in the USA. I pray to God for Russia to be free from its bad leader, who is bringing the world close to its end because of his huge ego still lingering from KGB failures in East Berlin. It is very sad, a great shame for us Slavic men. We need to stop following these bad rulers who take everything from us, leaving us with no hope. I pray for a democratic Slavic world, without this bad man. We Russian men say no to this government, don't believe Putin, USA. Russian people desperately want peace from this bad man. He's like an evil oil boss, similar to the characters in the first Dune movie, you understand? Putin even uses horses to carry his terrible ideas for the country while he punishes us severely in Siberian gulags for speaking against him. We want to be free, please have compassion; we are trapped and want the same freedom as the rest of the world. We desire no war; Putin is murdering anyone who doesn't obey his absolute evil authority. Slava ukraine.
Hello everyone,
I'm excited to share with you an instant messaging application I've been working on that might interest you. This is a chat app designed to work within your browser, with a focus on browser-based security and decentralization.
What makes this app unique is that it doesn't rely on messaging servers to function. Instead, it works based on your browser's javascript capabilities, so even low-end devices should work.
Here are some features of the app:
Your security is a top priority. Here's how the app keeps you safe:
The app is still in the early stages and I'm exploring what's possible with this technology. I'd love to hear your feedback on the idea and the current state of the app. If you have any feature requests or ideas, I'm all ears in the comments below!
Looking forward to hearing your thoughts!
Note 1: As a solo-developer, i dont have the capacity or knowlege to do anything like an "official launch". i expect the app will progressively get better with feedback from users (as it has so far).
Note 2: I think the app has (approximately?) reached a feature-complete state, but i'm not sure. I'm looking for feedback on what features are missing, and what features are not needed. The next step would be to grow the number of users by making the app more user-friendly and easier to use. (I need your help on this)
Note 3: The app is not open source yet (sorry), but im open to answering questions about how the code is working (more details can be found in the docs). Open sourcing the app is something i would like to do in the future, but not a priority right now. Some parts of the app are open source.
Note 4: The UI is a clunky implementation of Material-UI. It's something i will fix as i move towards open sourcing the UI components. i will take the opportunity to also give more attention to a "desktop friendly UI" (right now the app is best experienced on a mobile device).
Note 5: Id like to keep the wording i have for "pods" although i have recieved feedback about it not being clear what it means. A pod is what you might think of as like a "chat room" and will be further developed to support group-chat. you can create a pod with a connected peer in the contact-details-page. The wording "pod" comes from how a group of whales is called a pod.
I’m new to this but very interested in creating a mesh network over a 5-10 mile suburban area using multiple LoRas. So long distance is a priority which I know creates greater latency considerations, but this is emergency communications after all - I’m fine with it. My question is what are the specs I should be looking for to maximize the distance / power including the main unit, antenna and anything else.