by 1970-01-01
4 subcomments
- 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.
https://datatracker.ietf.org/doc/html/rfc8981#name-problem-s...
- They should charge a small annual fee and let people reserve a custom word for a given IP. You could even have a small utility on your computer that automatically queries given names to "resolve" to IPs.
- I tried it. Maybe it's easier to speak than hexadecimal is.
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.
- Reminds me a bit of S/KEY (RFC1760, RFC2289 and others around the 1990's).
Not because of the encryption element, but the part about representing a 64 bit integer as a six word sequence for usability.
(https://en.wikipedia.org/wiki/S/KEY#Usability).
Also used outside of that for quickly/easily recognising hash fingerprints.
(It's easier to recognise that your fingerprint is "GAFF WAIT SKID GIG SKY EYED" than "87FE C776 8B73 CCF9").
(It also slips some parity in there for good measure).
- 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.
by Gathering6678
2 subcomments
- It reminds me of what3words, using three words to describe any location on earth. I really hoped that could catch on.
by Waterluvian
3 subcomments
- 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.
I’d really love to see things like this generate little jingles along with the sentence. :)
- The new times take now beneath the new time while new times take the new year.
Or more concisely, localhost.
- I would have enjoyed a blog entry detailing how this works, regardless of its practical utility.
by Brajeshwar
0 subcomment
- I’m afraid to ask, but why, and who, tries to or wants/needs to remember IPv6 addresses?
by al_borland
1 subcomments
- 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.
- It'd be nice if simpler addresses gave simpler sentences. fe80::1 translates to "Uninhibited times take now inside new time yet new times take the new year."
- "The amazing champions inspire boldly like brilliant genius and incredible legends admire splendid talent."
Hard to forget a sentence like that!
by RedShift1
1 subcomments
- 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?
- The new times take now beneath the new time while new times take the new time.
- 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?
- http://borg.uu3.net/~borg/?ipv6
Now, if only those people who designed IPv6 were smarter.. Hex aint that bad, LONG hex addresses are pain to use.
Now, lets say you have LAN like this [::1:0:0/56]. So, ::1:0:24 is easy to remember right? Managable? right?.. Also, bonus for :: shortening is, you immediatly know what are you dealing with, ::1 is loopback, ::1:1 is LL, ::1:0:1 is LAN.. everything else is Internet.
The truth is, IPv6 is really 64bit, the other 64bit part is just randomish node address...
by dpc_01234
2 subcomments
- This encoding is so long, that I'm more likely to remember the raw address. :D
And I don't think I ever typed manually any IPv6 address other than `::1`.
- The first (of two) examples encodes to:
> How now the smart flies take the new time beyond new time where new times come.
..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.)
by Singletail
0 subcomment
- I'm old. I can't remember breakfast.
- why is there even a need to remember IPv6 address in the first place?
- Not too sure of the utility of this. It's not an easy 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.
All that being said, I think it's a neat idea and a cool tool!
- love to get an api for this.
- 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.
by emilfihlman
1 subcomments
- Just proves that 16 bytes was too much, and we should have just gone 8 bytes.
by blurrybird
0 subcomment
- Mine comes with a swear!
[…] thaw the new case beyond pure mass where flagrant toys fucken.
by paulsutter
3 subcomments
- ipv6 is for faceless hordes of cellphones, which could just as easily be NAT
despite being an ipv6 skeptic, i’ve been thinking to try using ipv6 for our new company network, but make the addresses purely readable
Hacker News