IdeaWell

Project ideas from Hacker News discussions.

Modern email can be built from borrowed parts

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. First‑contact consent & “requests” folder

"First-contact consent: an unknown sender doesn't get into the mailbox; they land in a "requests" box with their first message visible (like Signal's message requests). You accept, and the thread opens forever. A stranger can knock on your door, which is the essential property of mail, but they can't fill up your living room." – amelius

2. Backward compatibility & migration concerns

"I think the network effects make email hard to replace, virtually everyone online has an email address. If this could include a migration path, with backwards compatibility with SMTP, I think it would have a better shot of getting adoption." – 8organicbits

3. Better UI and thread/sub‑conversation handling

"You do get it on chat services, but there's no option there to create sub‑conversations." – TheOtherHobbes

🚀 Project Ideas

Generating project ideas…

First‑Contact Consent Mailbox (FCCM)

Summary

  • Unknown senders are placed in a “Requests” folder where the first message is visible; users must explicitly accept to open the thread permanently.
  • Provides a consent‑based inbox that replaces spam filtering while preserving the ability to reply forever.

Details

Key Value
Target Audience Privacy‑savvy professionals and small businesses that receive cold outreach
Core Feature Server‑side challenge for new domains; configurable postage or trust escalation before delivery
Tech Stack Node.js backend, PostgreSQL, WebPush, IMAP‑gateway library
Difficulty Medium
Monetization Revenue-ready: $5/mo

Notes

  • Directly addresses HN comments that praise “first‑contact consent” and liken it to Signal’s request flow.
  • Users want a default that keeps the inbox clean while still allowing legitimate first‑contact messages.
  • Easy fallback to standard SMTP via a lightweight gateway encourages adoption without breaking existing infrastructure.

ThreadHub Protocol (THP)

Summary

  • A modern HTTP‑based communication protocol that merges email and chat semantics with structured sub‑conversations.
  • Enables clean topic tagging, export, and trust‑chain verification for better thread management.

Details

Key Value
Target Audience Community organizers, developers, and power users who need topic‑centric messaging
Core Feature Named threads with auto‑export to markdown and Web of Trust key rotation
Tech Stack Rust server, SQLite, HTTP/2, TypeScript client SDK
Difficulty High
Monetization Hobby

Notes

  • Responds to HN calls for “sub‑conversations” and the ability to split and archive discussions cleanly.
  • Users highlighted the difficulty of forwarding specific threads to external parties (e.g., lawyers) in current email clients.
  • The protocol design stays compatible with HTTP infrastructure while introducing richer messaging concepts.

MailBridge Gateway

Summary

  • A SaaS gateway that translates existing SMTP traffic into the consent‑based FCCM model and adds thread‑management UI.
  • Allows users to retain their existing email addresses while gaining modern inbox controls.

Details

Key Value
Target Audience Small email hosting providers, freelancers, and solo practitioners using custom domains
Core Feature Transparent integration layer with configurable auto‑approval whitelist and request‑folder UI
Tech Stack Python FastAPI, Docker, Redis
Difficulty Low
Monetization Revenue-ready: $2/mo per mailbox

Notes

  • Meets demand for “fallback to SMTP” and migration paths discussed on HN.
  • Users expressed interest in keeping their current address but improving the inbox experience without abandoning legacy setups.
  • Simple pricing and easy deployment make it attractive for niche markets seeking immediate productivity gains.

Read Later