Why would you be typing of remembering ipv6 addresses? Representation has always been consistent, if you learn the rules, like how 1337::1/64 is a valid address.
curl URL Format curl -6 "[2001:db8::1]:8080/"
wget URL Format wget "[2001:db8::1]"
ssh Standard Login ssh user@2001:db8::1
ssh Specified Port ssh -p 2222 user@2001:db8::1
scp Remote Path scp file.txt [2001:db8::1]:/tmp/
rsync Remote Path rsync -av file.txt [2001:db8::1]:/tmp/
nc (netcat) Positional nc -6 2001:db8::1 80
telnet Positional telnet 2001:db8::1 80.
nmap Target nmap -6 2001:db8::1So any place that can only take addresses, not some sort of URL, should/can (of course, the program author can do whatever he/she wants!) accept addresses without delineation.
90% of HN replies are debating trivialities to attempt to skirt the point. The point is that ipv6 usability is worse. CLI usability is a good example.
There are many benefits to ipv6, but let’s at least admit the faults so they can be addressed and encourage further adoption.