IdeaWell

Project ideas from Hacker News discussions.

.name Termination

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Prevalent themes in the Hacker News discussion about Verisign’s termination of third‑level .name domains

  1. Verisign’s reputation and profit‑motivated actions
    Users repeatedly label Verisign as “scummy” or “the worst,” accusing it of putting revenue above user impact.

    “Verisign is the worst. Hope author wins” – xyst
    “They have been generally scummy throughout their existence.” – gpvos

  2. Loss of personal online identity and services
    Commenters worry that deleting first.last.name breaks email, IoT devices, and long‑established personal branding.

    “Second, my email address also disappears. Third, all the IoT devices that use services on this domain become bricks.” – drnick1
    “One domain gives you access to tens of thousands of users email. It seems like a privacy nightmare.” – jonhohle

  3. Technical and architectural concerns with the .name TLD
    The lack of clear Public Suffix List entries raises cookie‑security and isolation issues, making the hierarchy confusing.

    “Since neither smith.name nor the wildcard *.name appear in the Public Suffix List, browsers would likely allow any page on a *.smith.name domain to set cookies for .smith.name.” – nneonneo
    “Surprisingly the public suffix list doesn't list *.name. So they're indeed not properly isolated from each other.” – CodesInChaos

  4. Sentimental practice of registering domains for newborns
    Several users share anecdotes of registering a child’s name minutes after birth, viewing it as a prideful or symbolic act.

    “Minutes after my daughter was born, I also registered beverly.fraser.name.” – eleventen
    “I registered a domain name for my son the day he was born… shows his birthday, which I found amusing!” – buzzy_hacker

  5. Calls for ICANN oversight and alternative solutions
    Participants criticize ICANN’s approval, suggest legal or regulatory pushback, and propose technical workarounds (e.g., honoring existing subdomains, closed auctions).

    “You might want to write to the CA attorney general.” – NewJazz
    “Since ICANN is a non‑profit that is required to operate in the public interest I do hope there can be some pushback on this.” – anominal
    Proposed fix: “Third level names where only one person has the second level domain should be transferred to whoever owns that single third level name.” – strenholme

🚀 Project Ideas

Generating project ideas…

NameShift: .name Migration Assistant

Summary

  • A web‑based toolkit that helps owners of third‑level .name domains (firstname.lastname.name) migrate their DNS, email forwarding, and IoT configurations to alternative domains before Verisign’s termination takes effect.
  • Core value: one‑click export of current zone files, automated suggestion of available equivalent names (e.g., firstname‑lastname.name or firstname.lastname.tld), and step‑by‑step transfer guides for popular registrars.

Details

Key Value
Target Audience The ~22,000 individuals/families who own firstname.lastname.name domains and rely on them for email, personal sites, or IoT device configuration
Core Feature Export DNS records, generate migration checklist, registrar‑agnostic transfer instructions, and optional automated DNS updates via API (e.g., Cloudflare, Namecheap)
Tech Stack React + TypeScript frontend, Node.js/Express backend, PostgreSQL for user data, integration with registrar APIs (REST) and Public Suffix List for name availability checks
Difficulty Medium
Monetization Revenue-ready: Subscription $4/mo per domain (free tier for basic export)

Notes

  • HN commenters expressed urgency: “I registered beverly.fraser.name … minutes after my daughter was born” (eleventen) and fear of losing “email address also disappears” (drnick1). NameShift directly addresses the need to preserve those identities.
  • Provides a practical utility that could spark discussion on best migration practices and reduce the scramble for squatters.

ForeverMail: Stable .name Email Forwarding

Summary

  • A hosted email forwarding service that lets users keep their firstname@lastname.address forever, even if the underlying .name domain is lost, by forwarding to any real mailbox and allowing seamless destination updates.
  • Core value: decouples the public email address from the volatile registrar, giving users a permanent personal address they control.

Details

Key Value
Target Audience .name domain holders who use firstname@lastname.name for personal or family communication (e.g., “I use first@unusual.name … for my family” – decimalenough)
Core Feature Immutable alias (firstname@lastname.name) that forwards to user‑chosen mailbox; web dashboard to change forward target, view logs, and enable SPF/DKIM for outbound mail via relay
Tech Stack Mail server (Haraka or Mail-in-a-box) on Docker, API layer (Go), Redis for rate limiting, frontend (Svelte), DNS management via RFC2136 updates
Difficulty Medium
Monetization Revenue-ready: $2/mo per alias (discounts for bundles of 5+ aliases)

Notes

  • Users lamented losing email access: “my email address also disappears… IoT devices that use services on this domain become bricks” (drnick1). ForeverMail solves this by making the address independent of the domain.
  • Could become a community‑run service, fostering discussion on email sovereignty and alternative trust models.

VeriSignWatch: Registry Change Monitor & Advocacy Hub

Summary

  • A monitoring service that watches ICANN proposals, Verisign filings, and public comment periods for the .name TLD, sending real‑time alerts and providing one‑click tools to submit comments or join collective actions.
  • Core value: empowers the .name community to stay informed and act swiftly against unfavorable registry changes.

Details

Key Value
Target Audience .name domain owners, activists, and legal advocates concerned about registry stability (e.g., “I will be writing to the CA AG myself” – anominal)
Core Feature RSS/Webhook alerts for new ICANN/Verisign documents, keyword highlighting (.name, termination, price cap), templated comment submission, and a public ledger of community responses
Tech Stack Python scraper (Scrapy) + FastAPI backend, PostgreSQL, React dashboard, WebSocket for live alerts, optional integration with GitHub for comment tracking
Difficulty Low
Monetization Hobby (ads/sponsorships optional)

Notes

  • Commenters asked for ways to fight back: “Lawyer up and fight it. This is bs.” (rburhum) and “I will be writing to the CA AG myself.” VeriSignWatch gives them the tooling to do so efficiently.
  • Encourages HN discussion on registry governance and collective bargaining power.

NameLegacy Marketplace: Alternative TLD Broker for Family Names

Summary

  • A curated marketplace that helps .name holders register equivalent second‑level domains in newer, stable TLDs (e.g., .family, .me, or country‑code domains) and offers bulk discounts, escrow‑based transfers, and automated DNS setup.
  • Core value: provides a trusted, low‑friction path to secure a lasting family‑name online presence without relying on the volatile .name registry.

Details

Key Value
Target Audience Families and individuals seeking a permanent, recognizable domain for their surname (e.g., “pick any TLD and register fraser.tld” – Ecco)
Core Feature Search tool for available firstname‑lastname.tld or lastname.tld variants, bulk purchase cart, optional escrow service for name transfers, and one‑click DNS configuration via provider APIs
Tech Stack Next.js frontend, Node.js backend, integration with multiple registrar APIs (OpenSRS, Enom), Stripe Connect for payments, PostgreSQL for inventory
Difficulty Medium
Monetization Revenue-ready: 10% transaction fee on each domain sale (minimum $2)

Notes

  • Users discussed alternatives: “Why not register fraser.name directly? Or pick any TLD and register a 2nd‑level domain?” (Ecco). NameLegacy makes that concrete and safe.
  • Marketplace could spur discussion on the economics of alternative TLDs and the viability of family‑name branding.

DIDName: Decentralized Identifier Layer for .name

Summary

  • An open‑source service that maps existing firstname.lastname.name domains to a Decentralized Identifier (DID) document stored on IPFS or a blockchain, allowing email, web, and IoT services to resolve via the DID rather than the registrar‑dependent DNS name.
  • Core value: future‑proofs personal identifiers against registry takedowns while preserving human‑readable .name addresses for backward compatibility.

Details

Key Value
Target Audience Tech‑savvy .name owners interested in self‑sovereign identity (e.g., “we need a fully decentralized TLD alternative” – psychoslave)
Core Feature DID creation service that links a .name domain to a DID document containing public keys, service endpoints (email, web), and resolution via did:web or did:ipt; includes resolver library and email gateway (DIDComm → SMTP)
Tech Stack Rust or Go for DID core, IPFS/Filecoin for storage, JavaScript resolver library, SMTP relay (Haraka), optional Ethereum L2 for anchoring, React admin UI
Difficulty High
Monetization Hobby (grant‑funded or donations)

Notes

  • Commenters dreamed of decentralized options: “So, where is our fully decentralized TLD alternative…” (psychoslave). DIDName offers a pragmatic stepping stone using existing .name as an anchor while giving users portable keys.
  • Could stimulate HN debate on DID adoption, email decentralization, and resistance to registrar arbitrariness.

Read Later