News for hackers. Stuff that matters.
Re:Why IPv6 is the only way forward by Hikikomori on Wednesday April 08, 2026 @02:14PM (#47694113)
No fibbing. Network devices don't use brackets.
Re:Why IPv6 is the only way forward by tonymet on Wednesday April 08, 2026 @06:24PM (#47697062)

  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::1
Re:Why IPv6 is the only way forward by BenjiWiebe on Saturday April 11, 2026 @12:48PM (#47732028)
This is kinda arguing semantics, but: The address doesn't use brackets.You include brackets to delineate the address, if the address-containing string could include colons already.

So 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.

Re:Why IPv6 is the only way forward by tonymet on Sunday April 12, 2026 @01:01PM (#47741951)
List all of the network CLI tools that need brackets or even shell escapes for ipv4 addresses.

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.