IdeaWell

Project ideas from Hacker News discussions.

Show HN: Flipflop – Iroh-powered persistent tunnels for filesharing

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Theme 1: Prioritize native/bare‑metal efficiency before browser support
- “We think it is better to make it extremely efficient on bare metal first, and then grow into the restricted browser ecosystem where possible.” — rklaehn
- “Why native code?” — StartingAbusine (questioning the focus on native implementations)

Theme 2: Browser use is limited; most implementations rely on relays or WASM
- “WebRTC only works in very specific conditions, most of the time you'll need a TURN server anyway, so it's probably better to just use an Iroh relay (you can run your own).” — andunie
- “We currently support the browser via WASM, but only with relay mode.” — rklaehn

Theme 3: Real‑world applications, comparisons, and the decentralized vision
- “You can't build a decentralized social media ecosystem on top… Like Iroh, best to use a central server. So then you have legal liability for your users.” — synctext
- “In Flipflop you don't need anything besides the app, and each two peers form a 'network' of their own, with no owner and no management.” — andunie (contrasting Flipflop with Taildrop/Tailscale)
- “If you are in an extremely weird NAT you will fall back to a relay… a p2p social application that occasionally uses a relay is very much preferable to a centralised app.” — rklaehn

🚀 Project Ideas

Generating project ideas…

Iroh Browser Bridge – WebRTC‑enabled P2P peer for browsers

Summary

  • Enables browsers to act as native Iroh peers via WASM + WebRTC, removing the need for forced relay use.
  • Provides direct browser‑to‑device P2P tunnels for file transfer, messaging, or IoT streams without third‑party relays.

Details

Key Value
Target Audience Web developers, power users who want to share files or data from a browser to personal devices
Core Feature Iroh peer identity compiled to WASM, WebRTC signaling for NAT traversal, automatic relay fallback only when needed
Tech Stack Rust (Iroh) → WASM, WebRTC API, lightweight signaling server (Node.js or Rust/Actix), optional STUN/TURN
Difficulty Medium
Monetization Hobby

Notes

  • Commenter StartingAbusine asked: “Why native code? I would think this could be done completely in the browser using WebRTC?” – this idea directly satisfies that request.
  • HN discussion highlighted frustration with relay reliance and the desire for browser‑native P2P; a bridge would let users keep data off third‑party servers while still benefiting from Iroh’s robust connection logic.
  • Potential utility: decentralized web apps, peer‑to‑peer file sharing pages, browser‑based IoT dashboards that can talk directly to home sensors.

Iroh Relay-in-a-Box – Self‑hosted relay manager with UI

Summary

  • Docker‑ized Iroh relay with a simple web UI for monitoring, configuration, and optional anonymous payment (ZCash) integration.
  • Lets anyone run their own private relay to avoid metadata leakage from public relays.

Details

Key Value
Target Audience Privacy‑conscious individuals, homelab operators, small teams wanting sovereign Iroh infrastructure
Core Feature One‑click Docker Compose deployment, UI showing live peer connections, traffic stats, TLS cert management, and optional ZCash‑based billing
Tech Stack Rust Iroh relay binary, Docker, simple React/Vue UI, Prometheus‑style metrics, optional ZCash RPC client
Difficulty Low‑Medium
Monetization Hobby

Notes

  • andunie noted: “WebRTC only works in very specific conditions, most of the time you'll need a TURN server anyway, so it's probably better to just use an Iroh relay (you can run your own)”. This product makes that “run your own” trivial.
  • Commenters expressed interest in running personal relays for improved privacy and to avoid reliance on third‑party infrastructure; a packaged solution lowers the barrier to entry.
  • Potential utility: private relay networks for communities, edge‑relay deployments for IoT, or a foundation for a decentralized “generic Internet infrastructure” as envisioned in the thread.

Flipflop Share – Cross‑platform, account‑free file transfer using Iroh

Summary

  • Enables instant, no‑account file sharing between any of your devices using Iroh tunnels, QR‑code pairing, and optional relay fallback.
  • Works on desktop, mobile, and NAS‑like devices without needing a central service or sign‑up.

Details

Key Value
Target Audience Personal users with multiple devices (laptops, phones, NAS, IoT) who want simple, private file transfer
Core Feature Pair devices via QR code or short code, establish Iroh P2P tunnel, transfer files/folders with progress UI, background sync, automatic relay fallback when needed
Tech Stack Flutter (or React Native) for UI, Iroh Rust library via FFI/Tauri for desktop, optional self‑hosted or public relay
Difficulty Medium
Monetization Hobby

Notes

  • andunie praised Flipflop: “In Flipflop you don't need anything besides the app, and each two peers form a 'network' of their own, with no owner and no management.” This idea extends that philosophy to a polished, cross‑platform experience.
  • kkapelon quoted the README: “Use it to share stuff between all your devices” – highlighting the demand for exactly this capability.
  • Potential utility: replaces cloud‑based sync for ad‑hoc transfers, enables secure sharing of large media, and can serve as a building block for decentralized apps that need device‑to‑device data movement.

Read Later