IPv6 address, as a sentence you can remember

Original Article ↗ Hacker News Discussion ↗

Overall reaction to IPv6→sentence tool

  • Many find the generated sentences too long, awkward, and hard to memorize compared to short IPv6 examples like 2001:db8::1.
  • Several say they’d sooner remember the raw hexadecimal address than the produced sentences.
  • Some view it as a fun / April Fools–style toy rather than something with a real use case.
  • A few think it’s “neat” conceptually and would like an API or open-source algorithm.

Memorability & cognitive angle

  • Multiple comments note that nonsense but grammatical sentences are not necessarily memorable.
  • Comparisons are made to “correct horse battery staple”; the generated phrases lack that simple, vivid quality.
  • Others point out that music, rhyme, and meter dramatically improve memorization and suggest jingles would work better than plain sentences.

“Why remember IPv6 at all?”

  • Several argue that if you’re memorizing IPv6 addresses, you’re doing it wrong:
    • Use DNS / local names (.home.arpa, .local, etc.).
    • Use temporary addresses and privacy extensions instead of stable, memorable ones.
  • Others counter that static or known addresses can be useful (e.g., for home gateways, DNS servers, self-hosted services), and some do memorize IPv4 today.

IPv6 addressing practices

  • Suggestions for human-friendlier IPv6 on LANs:
    • Simple ULAs like fd10::1, or structured patterns mirroring IPv4 subnets.
    • Deterministic SLAAC based on MAC for stable internal addresses.
    • Short, “readable” prefixes plus DNS (sometimes split-horizon).
  • Some ignore RFC guidance about random ULA bits for convenience, accepting potential future renumbering.

IPv6 adoption & philosophy

  • One side: IPv6 “already happened”, usage to major services keeps rising; some countries are near-universal deployment.
  • Other side: adoption is still under 50% globally, seen as slow; skepticism that mass users “demand” IPv6.
  • Debate over NAT/CGNAT:
    • Pro-NAT view: not a sin; helps privacy and obviates globally routable endpoints; IPv6 adds complexity and privacy risks.
    • Anti-NAT view: middleboxes hinder protocol evolution; IPv6 restores end-to-end connectivity and simplifies self-hosting.

Analogies & alternatives

  • Frequent comparison to what3words:
    • Both map numbers to words; critics say word-based systems can be error-prone, proprietary, or non-navigable.
  • Some jokingly reinvent “DNS” in the thread as a superior, already-existing name-to-address system.