IdeaWell

Project ideas from Hacker News discussions.

Blackholing My Email

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1️⃣ Email is fundamentally broken and hard to fix

"There’s nothing to fall through, email fits it’s exact purpose. Email is supposed to have 0 sending/receiving friction." — righthand

The discussion repeatedly points out that spam, reputation‑based filtering, and ever‑changing standards make genuine improvement difficult, and people are frustrated with the status quo.

2️⃣ Email’s design remains surprisingly resilient despite the hurdles

"While increasingly difficult to get self‑hosted email to be accepted by the big providers like Google and Microsoft, it is still great to at least have the option of hosting a universally accepted form of communication yourself." — MattTheRealOne

Even as self‑hosting grows tougher, many still value email’s universal reach and see it as a stable, if imperfect, backbone of online communication.

3️⃣ The conversation drifted to admiration for the creator of de_dust2

"The fact that the author of the article is the author of de_dust2 is the real highlight!" — 3form

Users expressed surprise and appreciation upon learning that the well‑known Counter‑Strike map maker also authored the article, sparking a side conversation about the map’s impact.

🚀 Project Ideas

InboxGuard

Summary

  • A privacy‑first email gateway that only accepts messages from verified senders you’ve pre‑approved, eliminating unwanted marketing while preserving easy replies.
  • Solves the “fall through” problem by enforcing a whitelist‑plus‑verification flow without manual address‑book updates.

Details

Key Value
Target Audience Power users, privacy advocates, small businesses, freelancers who receive lots of verification emails
Core Feature Auto‑generated verification links for new senders, persistent whitelist rules, optional “fallback” inbox for unknown senders
Tech Stack Node.js backend, PostgreSQL, WebSocket for real‑time status, React front‑end, OAuth2 for sender verification
Difficulty Medium
Monetization Revenue-ready: subscription $5/mo per user

Notes

  • HN commenters often lament the “everything‑gets‑through” nature of email; a whitelist that only requires one click per new sender would be instantly appealing.
  • Could integrate with existing providers via OAuth, making adoption painless and sparking discussion about open‑source alternatives.

MailWarm#Summary

  • An AI‑driven warm‑up service that builds and maintains a healthy sending reputation for new email domains or IPs, preventing spam‑folder placement.
  • Addresses the “not enough reputation” barrier that blocks new senders despite correct SPF/DKIM/DMARC setup.

Details

Key Value
Target Audience SaaS startups, developers launching new transactional email services, marketers with fresh domains
Core Feature Automated, gradual volume ramp‑up with personalized content, adaptive throttling, reputation scoring dashboard
Tech Stack Python microservices, Elasticsearch for analytics, Redis for caching, Docker/Kubernetes deployment, React dashboard
Difficulty High
Monetization Revenue-ready: tiered pricing based on email volume (e.g., $10/mo for up to 5k emails/day)

Notes

  • The community frequently mentions reputation as the biggest hurdle for self‑hosted mail; a tool that hands you a “clean bill of health” would be a go‑to utility.
  • Could be open‑sourced as a framework, encouraging contributions and building a marketplace around reputation‑boosting plugins.

EmailBridge

Summary- A federated email routing layer that abstracts over multiple providers (Gmail, Outlook, custom SMTP) and centralizes spam filtering using shared community signals.

  • Tackles the fragmentation described by users who must manage reputation across disparate services.

Details

Key Value
Target Audience Developers building email‑centric apps, indie SaaS founders, privacy‑focused users who want consistent spam handling across providers
Core Feature Unified API for sending/receiving, shared spam‑filter model trained on aggregated user feedback, opt‑in “bridge nodes” for resilience
Tech Stack Go microservices, gRPC for low‑latency calls, PostgreSQL for storing shared models, WebRTC for direct peer verification, Angular UI
Difficulty High
Monetization Hobby (open‑source core, optional paid premium features for advanced analytics)

Notes

  • HN threads often discuss how each provider has its own spam policies; a communal filter that learns from many eyes would be a unique value proposition.
  • Could spark dialogue around decentralization of email and provide a practical, tangible utility for those frustrated with siloed spam handling.

Read Later