India ordered GitHub to pull Bitchat from its platform. The messaging app vanished from the centralized repository within hours. Yet copies of its source code surfaced almost immediately on Radicle, a peer-to-peer network where no single company controls the data. Developers mirrored the entire project. Anyone could clone it. The code lived on.
This episode, unfolding in recent days, highlights the limits of traditional code hosting. It also shows the strengths of systems like Radicle. The platform, built on Git, lets repositories replicate across user nodes without a central authority. Radicle.dev describes it as an open source, peer-to-peer code collaboration stack. No entity owns the network. Users stay in full control of their data and workflow.
Bitchat itself pushes those ideas further. The iOS and macOS app combines Bluetooth mesh networks for offline chats with the Nostr protocol for online reach. No accounts. No phone numbers. No servers. “It’s the side-groupchat,” its README states plainly. The project sits at rad:z2v9tRJz1oknFAqCSY5W5c76nVvm6 on a Radicle node. Its latest commit fixes geohash resolution for low-precision locations. The repository tracks changes from any peer. One delegate approves patches for the canonical branch.
Recent events brought Bitchat into sharp focus. Indian authorities gave GitHub three hours to remove the app, according to posts circulating on X. The deadline passed. The app reappeared on Radicle and other decentralized hosts. “India didn’t kill Bitchat,” one observer noted. “They just gave everyone a live demo of why decentralized networks exist.” The X post from @sudo_LakayPh captured the moment with a screenshot and sharp analysis. Similar chatter filled timelines, with users praising the rapid mirror to Radicle.
Radicle has matured since its early days. Version 1.0 launched in 2024, according to CryptoNews.net. Subsequent releases rolled out through 2026. The project hit 1.9.1 this May, as listed on its blog. A vulnerability disclosure accompanied some updates, showing attention to security. In March the team shifted domains to radicle.dev and radicle.network. These moves signal growing operational polish.
The network’s architecture sets it apart. Repositories replicate via gossip protocols. Issues and patches live as signed Git objects that travel with the code. Everything works offline once synced. “Radicle is architecturally local-first,” a Hacker News discussion observed. You run your own node. Browsing code, managing issues, reviewing patches happens against local data. No server round trips. Performance stays high.
Developers demonstrated this in practice. After the GitHub removal, the Bitchat codebase replicated to Radicle within hours. Seeding nodes multiplied. Each additional copy made takedown harder. The project’s public domain license removes barriers. Its WHITEPAPER.md and BRING_THE_NOISE.md files detail the technical choices. Bluetooth mesh supports up to seven hops. Messages use Noise protocol encryption. Nostr handles broader distribution with over 290 relays and NIP-17 for private messages.
Location-based channels add another layer. Geohashes create channels tied to physical areas. Precision ranges from block level down to country. A user in a protest zone might join a neighborhood channel without revealing identity. The app routes messages intelligently. Bluetooth first. Nostr as fallback. Smart queuing handles intermittent connections. Battery optimizations and duty cycling keep it practical on mobile devices.
But Radicle’s story runs deeper than one app. The platform emerged as a response to centralized platforms’ control. GitHub, GitLab and similar services offer convenience. They also create single points of failure and governance risks. Supply chain security suffers when one company can pull code or ban users. Radicle counters with cryptographic identities and peer replication. A 2021 blog post from Placeholder VC explained the vision. It integrated with Ethereum for names and funding. Projects could form DAOs. Developers gained portable identities immune to platform bans.
Progress continued. Radicle 1.0 marked a major milestone, per The Street. The team released a desktop app in 2025 to simplify issue management and patch reviews, as covered by LWN.net. The tool complements rather than replaces terminals and editors. A web explorer at radicle.network provides browser access. Recent talks at FOSDEM 2026, documented on FOSDEM.org, explored sovereignty and future network plans.
Adoption remains niche. Large repositories still pose challenges, though improvements in fetch and push operations help. Discussions on the NixOS forum considered mirroring nixpkgs to Radicle for resilience. The idea gained traction as a backup against potential disruptions. Yet most developers stick with familiar platforms. Convenience wins until it doesn’t.
Bitchat demonstrates what happens when pressure meets resistance. The app’s design matches its hosting. Both prioritize resilience over central control. Emergency wipe features let users clear data with triple taps. Private messages stay encrypted end to end. No central logs exist for authorities to demand. The mesh network forms spontaneously among nearby devices. Store-and-forward lets messages wait for physical proximity.
Critics point to practical limits. Bluetooth range restricts the mesh without enough participants. Seven hops help but don’t solve every scenario. Nostr integration adds complexity and potential metadata leaks, though the project minimizes them. Setup requires Xcode or command line tools for development. The public domain license invites contributions but offers no legal protections.
Still, the system works where others fail. Disaster zones. Censored regions. Offline events. Users in Nepal, Iran and Madagascar reportedly rely on similar mesh tools. Bitchat’s recent visibility could accelerate interest. Its Radicle presence ensures the code remains available regardless of corporate or government action.
The broader implications touch software supply chains. Centralized platforms face increasing scrutiny over content moderation, national security and economic leverage. Governments issue takedown orders. Companies comply. Decentralized alternatives shift the balance. No CEO to pressure. No single server to seize. The network persists through its participants.
Radicle’s team continues iterating. Releases in 2026 fixed bugs and added features. The vulnerability disclosure in March showed transparency. Community grants and an ecosystem growth fund support related work, though governance transitions toward token holders remain a work in progress. Heartwood upgrades introduced better gossip and verification, according to earlier roadmaps.
For now, Bitchat stands as both application and proof of concept. Its presence on Radicle proves the network’s value in real crisis. Developers cloned it. They seeded it. The project lives beyond any one platform. And that, more than any feature list, explains why such systems matter. They don’t just host code. They protect the ability to share it.
WebProNews is an iEntry Publication