IdeaWell

Project ideas from Hacker News discussions.

RSS feeds send me more traffic than Google

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

3 Prevalent Themes in the Discussion

Theme Core Insight Supporting Quotation
1. RSS’s shifting relevance – As AI summaries satisfy users, reliance on RSS (or direct clicks) may decline, especially for niche sites. “Is it possible that the users who used to find us through Google are now satisfied with AI chat summaries and no longer feel the need to click through to the actual page?” – ushimitsudoki
2. Skepticism about RSS metrics – Many argue that RSS traffic is largely automated, suffers from selection bias, and only reflects hits to their site, not genuine reads. “There's a ton of selection bias going on here.” – danpalmer
3. Modernising RSS with AI – Users propose AI‑driven clustering, embeddings, summarisation, and custom prompts to make feeds more useful and discoverable. “Just as a suggestion, but I've been thinking in terms of clustering.” – flir

These themes capture the community’s view that RSS remains a useful foundation but faces challenges from AI‑driven discovery, doubts about its analytics, and a push toward enhanced, intelligent feed tools.

🚀 Project Ideas

ReadPulse – Real‑Time RSS Readership Analytics

Summary

  • Provides publishers with lightweight, privacy‑first metrics on actual article reads from RSS subscribers.
  • Uses lazy‑loaded images and optional ?rss_ref= query parameters to capture click‑throughs without invasive tracking.
  • Delivers a simple dashboard showing read counts, geography, and referral source.

Details

Key Value
Target Audience Independent bloggers, newsletter writers, and small publishers who rely on RSS but lack analytics.
Core Feature Real‑time “read” detection via lazy image loading; referral tagging; anonymized geo‑lookup.
Tech Stack Backend: Node.js (Express) + Cloudflare Workers; DB: SQLite; Frontend: Vue.js; Image hosting via CDN; optional embed script for publishers.
Difficulty Low
Monetization Hobby

Notes

  • Addresses the exact frustration voiced by ushimitsudoki and tolerance about not knowing if RSS traffic translates to actual reads.
  • Simple embed can be added to any site, offering immediate utility and encouraging adoption among HN‑savvy creators.
  • Sparks conversation about ethical analytics for the open web and potential pushback from platforms that monetize page views.

FeedHive – Decentralized RSS Hub with Creator Revenue Share

Summary

  • A federated RSS reader where users subscribe to feeds on a peer‑to‑peer network, ensuring discoverability without algorithmic gatekeeping.
  • Built‑in micro‑payment system routes tiny payments (via Lightning Network or similar) to creators each time their feed entry is opened.
  • Includes optional clustering and tagging via community‑curated prompts.

Details

Key Value
Target Audience Privacy‑conscious readers, decentralization advocates, and content creators seeking sustainable income from RSS traffic.
Core Feature P2P subscription layer (using ActivityPub or libp2p), built‑in micro‑tip on article opens, community tagging via LLM.
Tech Stack Backend: Go (gRPC) + IPFS for content routing; Frontend: SvelteKit; Payments: Lightning Network via LNPay; Database: Badger.
Difficulty High
Monetization Revenue-ready: 5% platform fee on tips; optional premium plan for advanced analytics ($8/mo).

Notes

  • Directly answers flir’s desire for clustering and gnabgib’s frustration with selection bias, while giving creators a way to monetize RSS traffic.
  • Appeals to the “Make RSS Great Again” sentiment (the_70x) by restoring user control and reducing algorithmic manipulation.
  • Generates rich discussion topics around decentralization, payment for content, and the future of open web discovery.

Read Later