Reminds me a bit of S/KEY (RFC1760, RFC2289 and others around the 1990's).<p>Not because of the encryption element, but the part about representing a 64 bit integer as a six word sequence for usability.<p>(<a href="https://en.wikipedia.org/wiki/S/KEY#Usability" rel="nofollow">https://en.wikipedia.org/wiki/S/KEY#Usability</a>).<p>Also used outside of that for quickly/easily recognising hash fingerprints.<p>(It's easier to recognise that your fingerprint is "GAFF WAIT SKID GIG SKY EYED" than "87FE C776 8B73 CCF9").<p>(It also slips some parity in there for good measure).
If you're remembering your IPv6 address you're doing IPv6 wrong. In fact, it's good practice to always use a temporary IPv6 address.<p><a href="https://datatracker.ietf.org/doc/html/rfc8981#name-problem-statement" rel="nofollow">https://datatracker.ietf.org/doc/html/rfc8981#name-problem-s...</a>
I tried it. Maybe it's easier to speak than hexadecimal is.<p>But I'm not sure that "How morally the enviable assistances categorize the insistent iodine beyond new time where new systems stalk" has the same memorable quality as "correct horse battery staple" does.
Being essentially impossible to memorize is one of the worst attributes of IPv6. I memorize and manually type IPv4 addresses all the time and it's super useful.
I've been memorizing and typing IPv4 addresses too, but I have enough devices on the network now that I can't remember nearly all the IPv4 addresses.<p>So then I need to use DNS. At which point it could be IPv6.<p>I have 56 host entries in my dnsmasq.conf.
It is notable that an IPv4 address expressed as a decimal number has up to 10 digits, the same as a phone number in many countries.
DNS, Avahi are super usefuler.
What would have been your solution to needing more bits? More information is always going to be harder to remember.
Adding two extra bits to each octet, making each octet range from a still memorable 0-1023 rather than 0-255, would result in an addressing scheme 256x larger than all of IPv4 combined. The entire internet works fine even when IPv4 was nominally exhausted. NAT and CGNAT are not sins, they're not crimes, and there's no rational reason to be as disgusted with them as IPv6 fans are. Even then, IPv4 exhaustion wasn't really a true technical problem in the first place, it was an allocation problem. There are huge /8 blocks of public IPv4 space that remain almost entirely unused to this day.<p>The reason I'm an IPv4 advocate in the IPv4/IPv6 war is that the problem was "we're out of address", not "your thermostat should be natively routable from every single smartphone on the planet by default and inbound firewalls should become everyone's responsibility to configure for every device they own".<p>CGNAT is a feature, not a bug. Blending in with the crowd with a dynamic WAN IP is a helpful boost to privacy, even if not a one-stop solution. IPv6 giving everyone a globally unique, stable address by default is a regression in everyone's default privacy, and effectively a death sentence for the privacy of non-technical users who aren't capable of configuring privacy extensions. It's a wet dream for shady data brokers, intelligence agencies, organized crime, and script kiddies alike - all adversaries / attackers in threat modelling scenarios.<p>IPv6 adds configuration surface I don't want. Privacy extensions, temporary addresses, RA flags, NDP, DHCPv6 vs SLAAC — these are problems I don't have with IPv4. More features means more opportunities to footgun with misconfigurations, being forced to waste my time learning and understanding the nuances of each (in again, what amounts to system I want nothing to do with).<p>"Reaching your own stuff" is already a solved problem, too. Tailscale/Headscale gives you authenticated, encrypted, NAT-traversing connectivity. It's better than being globally routable. It's also opt-in for anyone who wants it, and not forced on anyone, unlike the IPv6 transition.
"The amazing champions inspire boldly like brilliant genius and incredible legends admire splendid talent."<p>Hard to forget a sentence like that!
It reminds me of what3words, using three words to describe any location on earth. I really hoped that could catch on.
Kind of like what3words, except what3words uses three words which you stand a chance of remembering, whereas this produced, for an address similar to mine, "Miniature nerves eulogize gaily inside erect lion yet able stables hiss the conclusive consultation."
what3words Is terrible and search and rescue teams are actively against people using it.
Something that I think was probably once obvious to me but I rediscovered recently is just how intensely wired for song the brain is. If you want to memorize anything, doing it as a song makes it far easier.<p>I’d really love to see things like this generate little jingles along with the sentence. :)
There actually was an attempt on HN a little while back to use GenAI to convert facts, flashcards, lists, etc. into automated melodic mnemonics. The biggest issue in that particular case was that it was also generating the motif from scratch.<p>At least for me, part of the reason I can still sing the countries of the world is because the original Animaniacs song was set to a tune that was already familiar: “Jarabe Tapatío” (aka the Mexican Hat Dance).
It's huge when you consider all the data humans have stored and transferred <i>orally</i> over the millennia.<p>Music, meter, and rhyme are all (among other things) algorithms for indexing and error-correction, tools very suitable to the squishy hardware.
The new times take now beneath the new time while new times take the new year.<p>Or more concisely, localhost.
This encoding is so long, that I'm more likely to remember the raw address. :D<p>And I don't think I ever typed manually any IPv6 address other than `::1`.
You can make unique local address subnets with simple addresses.<p>I use a simple one like `fd10::1/128` and `fd10::2/128` and so on<p>Technically speaking RFC 4193 says you should use random bits. But I don't care.
No need to type `::1` anymore, you can instead just type `The new times take now beneath the new time while new times take the new year.`
I don't understand how the mapping works. An address has 8 parts and produces 16 words, so each part consists of 2 words. If we take the example 2a02, that gets encoded to "how atop", but I don't see how that text helps me that "how atop" means 2a02? Am I suppose to memorize both? How does that help?
You are not supposed worry about the mapping. You trust the website to help decode it. You just remember the sentence. It's a little like what3words for coordinates.<p>The rationale being you are more likely to remember grammatical cogent sentence, than a random string of alphanumeric characters. Although I will agree that the generated sentences don't seem easy to remember. So I doubt it's utility.
What is the use-case for this? I’m trying to think of an IPv6 address I would need to remember, and then when I’d have access to this site without having access to a text file where I could have noted the address down. I’m coming up empty.
The new times take now beneath the new time while new times take the new time.
The first (of two) examples encodes to:<p>> How now the smart flies take the new time beyond new time where new times come.<p>..Nice idea, but it may need some more thought. (Even more so as 2001:db8::1 is much easier to remember than that!) (I wrote that parenthetical from memory on edit, vs. had to copy-paste the sentence when it was my intention to comment on it within seconds.)
So just imagine if there was a service that could translate any words you wanted into the IP address instead of relying on some website to generate jibberish. Wouldn't that be cool to use instead? Some kind of name system? Based around domains of authority?
I'm old. I can't remember breakfast.
Not too sure of the utility of this. It's not an <i>easy</i> sentence to remember, because while grammatical, it's nonsense—it would take some effort. So if I'm trying to memorize a static IP, setting up a DNS name is likely to be easier. And also if I'm going to be using this to memorize IPs I'd like the algorithm to be open source.<p>All that being said, I think it's a neat idea and a cool tool!
Ah yes, because "How now the smart flies take the new time beyond new time where new times come." is so much easier to remember than "2001:db8::1".
We kind of had the same idea for ECDSA public keys (an imagined solution to zokos triangle -- human readable and decentralized) as well as private keys (BIP39 brain wallets). Honestly it still falls short of truly name-based though.
Just proves that 16 bytes was too much, and we should have just gone 8 bytes.
Mine comes with a swear!<p>[…] thaw the new case beyond pure mass where flagrant toys fucken.
ipv6 is for faceless hordes of cellphones, which could just as easily be NAT<p>despite being an ipv6 skeptic, i’ve been thinking to try using ipv6 for our new company network, but make the addresses purely readable
If you're assigning addresses, you can make the addresses in a ULA as short as you want. You're supposed to use a random 40 bit network id but if you can accept that you may need to renumber at some point there is no reason you can't use fd12:b:a:d::beef or whatever.
There's another way to make addresses purely readable that's been around longer than NAT: DNS.