IdeaWell

Project ideas from Hacker News discussions.

.self: A new top-level domain designed to support self-hosting

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

5 prevalent themes in the discussion

  • TLD proliferation is seen as a “money‑grab” / commons‑pollution
    “It’s a commons‑pollution problem. Are we going to have to start thinking of every word with a dot in the middle as a potential name?” — HumanCCF

  • Self‑hosting empowerment is the core motivation
    “Our goal is for .self to be more than just another TLD string, we want to specifically empower the self‑hosting use case with local clients that integrate directly with the TLD and operate shared services like mail servers as a public good.” — HumanCCF

  • Enforcing “one person, one subdomain” raises abuse and verification concerns
    “Our rule of one person per subdomain will hopefully prevent this at scale, though it will admittedly be more difficult to examine any particular domain so closely.” — HumanCCF

  • High financial and bureaucratic hurdles
    “It costs ~$200,000 to apply for a new gTLD, and renewal fees are in the tens of thousands of USD.” — madsushi

  • Identity verification and abuse‑prevention require new tech (ZK proofs, heartbeats)
    “RISC Zero verifies that an exact computation was performed. What would be the point of the system otherwise?” — quotemstr

🚀 Project Ideas

SelfID Wallet

Summary

  • Enables any individual to claim a free .self subdomain by proving unique human identity via privacy‑preserving zero‑knowledge proofs (e.g., NFC passport or self‑sovereign ID).
  • Solves the “one person, one domain” verification problem without exposing personal data and prevents squatting.

Details

Key Value
Target Audience Hobbyist self‑hosters, homelab operators, privacy‑focused users
Core Feature ZKP‑based identity attestation that issues a cryptographic subdomain name tied to a verified person
Tech Stack Rust (zkvm), Node.js API, Cloudflare Workers, PostgreSQL, Ceramic/Identity, Cloudflare DNS API
Difficulty Medium
Monetization Hobby

Notes

  • Directly addresses HN commenters’ repeated call for a robust “one person, one subdomain” verification method.
  • Provides a public‑good alternative to costly ICANN applications and could serve as a proof‑of‑concept for future .self TLD deployment.

Homelab DNS Mesh

Summary

  • Free dynamic DNS and local DNS service that auto‑creates .self subdomains pointing to users’ home‑lab services, with built‑in heartbeat to keep domains alive.
  • Eliminates manual DNS record updates and solves the “no parking” problem.

Details

Key Value
Target Audience Home‑lab enthusiasts, DIY cloud providers, makers
Core Feature Automatic subdomain provisioning, TTL‑aware DNS, and usage‑based heartbeat validation
Tech Stack Go microservice, Cloudflare Workers, SQLite, Let's Encrypt, Webhooks
Difficulty Low
Monetization Hobby

Notes

  • Mirrors the popular “treat.your.self” idea, delivering catchy .self subdomains at zero cost.
  • Provides practical utility by making self‑hosted services reachable without paying for a registrar or dealing with squatters.

Community TLD Platform

Summary

  • SaaS that helps groups of self‑hosters collectively apply for a new gTLD (e.g., .self) and subsidizes the $227 k ICANN fee through sponsor donations and shared infrastructure.
  • Provides built‑in enforcement of “one person, one domain” and anti‑squatting rules.

Details

Key Value
Target Audience Non‑profits, open‑source projects, hobbyist communities
Core Feature Crowdfunded TLD application, shared registry backend, policy engine for domain allocation
Tech Stack Python/Django, PostgreSQL, AWS Route 53 API, Docker, Stripe for donations
Difficulty High
Monetization Revenue-ready: Subscription (tiered sponsor tiers)

Notes

  • Directly addresses the funding and legitimacy concerns raised by HumanCCF and other participants.
  • Aligns with the “public good” vision and would attract sponsors looking to back a community‑run TLD.

SelfDomain Marketplace

Summary

  • Free web interface where users can register a .self subdomain by linking a social account or government ID; the system validates “unique human” status and enforces non‑transferability.
  • Provides instant DNS hosting and automatic TLS certificates.

Details

Key Value
Target Audience Individuals wanting personal .self domains, developers of homelabs
Core Feature Identity‑based registration + automatic revocation after inactivity, built‑in email forwarding
Tech Stack Node.js/Express, Firebase Auth, Cloudflare DNS, Cert‑bot, Serverless functions
Difficulty Medium
Monetization Hobby

Notes

  • Mirrors the “one person, one domain” principle that HN users demanded, while solving the verification hurdle they highlighted.
  • Provides immediate practical utility: a ready‑to‑use .self address for services, avoiding squatting.

.self MailHub

Summary

  • Free email‑forwarding and lightweight mail server service for .self domains, handling SPF/DKIM/DMARC setup and rate‑limiting to prevent abuse.
  • Solves the email‑spam concern raised by commenters worried about “negative utility”.

Details

Key Value
Target Audience Homelab owners, personal bloggers, privacy‑oriented users
Core Feature Auto‑provisioned mailbox, built‑in spam filter, API for custom email aliases
Tech Stack Postfix + Amavis + SpamAssassin in Docker, Redis for rate‑limit, Cloudflare Workers for API
Difficulty Medium
Monetization Hobby

Notes

  • Directly answers the question “Why host your own mail server on .self?” by providing a turnkey, low‑maintenance solution.
  • Aligns with community desire for integrated email services tied to a personal domain without paying for traditional hosting.

Read Later