Bitchat is now on Radicle

Original Article ↗ Hacker News Discussion ↗

Bitchat, a decentralized messaging app that works over Bluetooth mesh networks and the Nostr protocol, has mirrored its code to the Radicle peer‑to‑peer code forge after the Indian government reportedly asked GitHub to remove the project. Commenters weigh its technical aims—offline, account‑less communication resistant to central control—against real‑world constraints like mesh network scalability, app‑store bans, and obscure hosting that may limit mainstream adoption. The move also highlights growing interest in decentralized code forges such as Radicle and Tangled, along with concerns about naming, usability, and the effectiveness of state censorship in the current social‑media environment.

What Bitchat Is and How It Compares

  • Described as a decentralized, peer‑to‑peer messaging app with two transports:
    • Local Bluetooth Low Energy mesh for offline communication.
    • Nostr protocol for internet-based messaging.
  • No accounts, phone numbers, or central servers; intended as a “side group chat.”
  • Distinct from Nostr/XMTP by its offline Bluetooth mesh focus.
  • Explicitly positioned against AT Protocol; uses Radicle instead of ATProto-based Tangled.

Mesh Networking & Technical Considerations

  • Bluetooth mesh is central; app is not IRC-compatible unless someone builds a bridge.
  • Questions about range (7 hops, ~100m each) are deferred to the project whitepaper.
  • General mesh networking constraints discussed:
    • “Always connected” mobile meshes don’t scale well beyond a few thousand moving nodes.
    • Store‑and‑forward, fragmented meshes may work better but limit rich media.
  • Ideas floated for overlaying BLE meshes across distance via VPN-linked relay nodes.

Hosting on Radicle and Project Infrastructure

  • Confusion over radicle.dev vs radicle.network:
    • Clarified as the same project: .dev for docs/protocol, .network for the network explorer.
    • Separation partly to avoid whole‑domain blocking due to user-generated content.
  • Some praise Radicle’s UI and suggest scripts to mirror arbitrary Git repos into Radicle.
  • One comment notes the Bitchat repo maintainer becoming unresponsive on F-Droid packaging; suggests forking.

Government Takedown Attempt & Censorship Debate

  • Context: Indian government reportedly requested GitHub remove Bitchat; links still appear accessible.
  • Some argue the action boosted visibility and pushed replication onto Radicle (Streisand-like effect).
  • Others counter that in today’s environment bans generally reduce usage, especially if app stores become involved.
  • Broader moderation discussion:
    • All large platforms are said to censor to some degree; moderation framed as necessary to combat spam/hate.
    • Disputes over perceived ideological bias in past Twitter moderation.
    • Legal shield for platforms (cited via Section 230) used to justify “private platforms can moderate as they wish.”

Adoption, Usage, and Alternatives

  • Field reports:
    • At a large festival (~80k people), ~20 devices detected; max observed path length ~2 hops, limiting coverage.
    • Some users in cities report seeing no peers; others report protest use, including in India.
    • Content so far ranges from near-empty to crude ASCII art.
  • Several note the novelty of texting without WiFi or cellular.
  • Prior Bluetooth/nearby‑only apps (e.g., FireChat, Berkanan, IR/infrared, AirDrop/hotspot name hacks) are mentioned for comparison, with commenters arguing Bitchat solves a broader, more autonomous mesh problem.

Name, Branding, and Culture

  • Many criticize the name as juvenile or awkward to say; others see it as an intentional edgy pun (similar to other joke titles).
  • Speculation that the name may be inspired by earlier IRC clients and that provocative names are sometimes an intentional branding choice.
  • Meta‑discussion about recurring “X is now on Y” HN posts and the tendency to mock whimsical names of open‑source projects more than corporate ones.