• lazynooblet@lazysoci.al
      link
      fedilink
      English
      arrow-up
      13
      arrow-down
      1
      ·
      edit-2
      9 months ago

      How did people visit sites using ipv6 addresses before this? Ipv6 has been around for years. Seems like a slow pickup

      • shortwavesurfer@lemmy.zip
        link
        fedilink
        arrow-up
        11
        ·
        9 months ago

        Well, on desktop it worked. So you could do it that way. But on mobile, what you had to do was go to a website like Google, add it as a bookmark, and then edit the bookmark and change the web address from Google to the IPv6 address.

    • fossphi@lemm.ee
      link
      fedilink
      English
      arrow-up
      7
      ·
      9 months ago

      I wonder why this wasn’t mentioned in the changelog. Seems substantial

      • shortwavesurfer@lemmy.zip
        link
        fedilink
        arrow-up
        7
        ·
        9 months ago

        Probably because most people are not accessing routers and web servers through their IPv6 addresses and instead they are using IPv4s like 192.168.1.1. I mean, come on, who does that?

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          9 months ago

          Yeah, typing an IPv6 address on my desktop I’d annoying enough, and way worse on my phone.

          It should still be supported, just not called out specifically.

      • p1mrx@sh.itjust.works
        link
        fedilink
        arrow-up
        4
        ·
        edit-2
        9 months ago

        That patch was my only contribution to Firefox, and I didn’t research how to update the user-facing changelog. When 122 hits my phone I’ll ping the bugs, to notify the 20 nerds who actually care about the problem. Typing IPv4/IPv6 literals is a pretty niche feature on the modern web.

        Currently https://play.google.com/store/apps/details?id=org.mozilla.firefox says “Version 121.1.0, Updated on Jan 19, 2024”