Replies: 1 comment
|
I was going rto write same idea For example, could the core protocol be exposed as a library, SDK, or local daemon so that other applications running on the device could exchange small structured messages through the Bitchat mesh? The idea would be something like: External app Instead of only sending chat messages, applications could publish and subscribe to small messages such as: { Possible use cases could include: Local-first app synchronization Of course, this would require clear limits: small messages, TTL control, app-level permissions, authentication/signatures, and protection against spam or mesh flooding. So my question is: Is there any plan, or would there be interest, in separating Bitchat into something like bitchat-core, bitchat-app, and maybe a future bitchat-sdk, so that Bitchat could become a reusable infrastructure protocol for other applications? I think this could make Bitchat much more than a chat app: it could become a decentralized local communication layer for many kinds of applications. |
Uh oh!
There was an error while loading. Please reload this page.
My idea is to create an open protocol inspired by the principles of bitchat, but with a broader scope: enabling any type of decentralized application to exchange information directly between devices, without relying on centralized infrastructure. The protocol would be based on mesh networking over Bluetooth Low Energy (BLE), with native support for automatic relays and multi-hop communication, ensuring resilience and extended reach.
Additionally, the protocol would optionally integrate bridges with the nostr network, allowing data to be moved between different mesh networks or synchronized whenever internet connectivity is available. In this way, it would be possible to connect multiple mesh clusters, expand the reach of information, and facilitate interoperability between communities and applications.
With this approach, developers could create everything from messengers to emergency coordination apps, local social networks, games, or file-sharing systems—all in a secure, anonymous way, without persistent traces. The open and modular architecture would allow new types of apps and use cases to emerge, forming a true decentralized and private “internet,” where each participant owns their data and identity.
The protocol would be publicly documented, referencing the bitchat implementation, and would provide specifications for peer discovery, routing, end-to-end encryption, message fragmentation, caching and forwarding, as well as interfaces for integration with alternative transports such as WiFi Direct, LoRa, or ultrasound. The goal is to foster a new generation of decentralized, interoperable, and censorship-resistant apps, built on a common and open foundation.
What do you think about this?
All reactions