IdeaWell

Project ideas from Hacker News discussions.

Peerweb: Decentralized website hosting via WebTorrent

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Technical feasibility is still a hard problem
Many commenters point out that browsers simply aren’t “real torrent clients” and that discovery, STUN, and DHT work‑arounds are fragile.

“If browsers had real torrent clients we would be having a very different conversation.” – dcreater
“The problem is that browsers cannot be real torrent clients and open connections without some initial routing for the discovery.” – embedding‑shape
“I tried this, the functional ‘Functionality test page’ is stuck on ‘Loading peer web site… connecting to peers’.” – logicallee

2. Moderation, copyright, and censorship concerns dominate the debate
Participants repeatedly warn that a P2P web host can’t enforce rules, making illegal or copyrighted material easy to spread.

“I think it is very difficult (and dangerous to the host) to serve user‑uploaded videos at scale, particularly from a moderation standpoint.” – NewsaHackO
“IPFS however has no means to track the author or the license of content.” – grumbel
“I can't imagine that Peerweb has much in the way of stopping certain types of material from being uploaded.” – SLWW

3. Usability and performance are major roadblocks to adoption
Even when the idea works in theory, demos are slow, buggy, or unusable, which keeps users from trying it.

“It takes > 5 seconds to load a page.” – dpweb
“The demos don’t work for me.” – davidcollantes
“I tried this, the functional ‘Functionality test page’ is stuck on ‘Loading peer web site… connecting to peers’.” – logicallee

These three themes—technical limitations, moderation/legal risks, and poor user experience—capture the core concerns voiced in the discussion.

🚀 Project Ideas

PeerSite

Summary

  • A browser‑extension + lightweight desktop helper that turns any static website into a self‑hosted, P2P‑served site using WebTorrent.
  • Eliminates the single point of failure by letting visitors download content from peers instead of a central server.
  • Provides an intuitive UI for uploading, generating magnet links, and sharing a short “peer‑link” that works in any browser.

Details

Key Value
Target Audience Indie web developers, hobbyists, small‑business owners who want zero‑cost hosting.
Core Feature Automatic WebTorrent seeding of site assets, peer discovery via a lightweight DHT, and a “peer‑link” that bypasses traditional DNS.
Tech Stack Chrome/Firefox extension API, Node.js desktop helper, WebTorrent library, libp2p‑DHT, optional IPFS gateway fallback.
Difficulty Medium
Monetization Hobby

Notes

  • Users like elbci and dtj1123 want a way to share links that aren’t just magnet links; PeerSite gives a simple URL that works in any browser.
  • The demo sites in the discussion often fail to load; PeerSite’s UI will show peer health and fallback to CDN if needed.
  • Great for quick experiments, community projects, and as a learning tool for P2P web tech.

P2P DNS Resolver

Summary

  • A browser plugin that resolves .p2p domains by querying a permissionless blockchain for signed DNS records and then fetching content via WebTorrent or IPFS.
  • Provides censorship‑resistant, decentralized domain resolution without relying on a central DNS server.
  • Users can publish their own .p2p domains by signing records with their private key.

Details

Key Value
Target Audience Developers, privacy advocates, activists needing censorship‑resistant domain names.
Core Feature Blockchain‑backed DNS records, WebRTC‑based peer discovery, fallback to public gateways.
Tech Stack Ethereum or Solana smart contract, Web3.js, libp2p‑DHT, WebRTC, browser extension.
Difficulty High
Monetization Revenue‑ready: subscription for premium DNS analytics + optional paid domain registration.

Notes

  • The discussion highlights the lack of a decentralized DNS; this solves that pain point directly.
  • Users like recursivegirth and theendisney want a “blockchain ledger as an authoritative source for DNS records”; this product implements that.
  • Enables sharing of content via “https://myapp.p2p” without a central server, addressing elbci’s single‑point‑of‑failure concern.

P2P Video Hub

Summary

  • A JavaScript library that turns any <video> element into a P2P‑streamed video using WebRTC data channels and WebTorrent.
  • Automatically seeds the video, discovers peers, and falls back to a CDN if peer bandwidth is insufficient.
  • Includes a simple UI for “re‑hosting” videos from trusted peers, mitigating moderation concerns.

Details

Key Value
Target Audience Content creators, small video platforms, educators wanting low‑cost, scalable video hosting.
Core Feature P2P video streaming, auto‑seeding, peer‑to‑peer load balancing, CDN fallback, moderation via whitelist.
Tech Stack WebRTC, WebTorrent, Node.js signaling server, optional IPFS integration, React component wrapper.
Difficulty Medium
Monetization Revenue‑ready: pay‑per‑GB for CDN fallback + optional premium analytics.

Notes

  • Addresses the frustration that “video hosting at scale is expensive” (NewsaHackO, zkhrv).
  • Provides a “simple JS wrapper” that developers can drop into any site, solving the “no easy integration” pain point.
  • The library’s fallback mechanism ensures that even if peers are slow, viewers still get a smooth experience, tackling the “>5 sec load” issue raised by dpweb.

Read Later