Skip Navigation

You're viewing a single thread.

20 comments

  • That base64 is so long, and doesn't need to be. An IP address is 4 bytes so it could be represented as simply 8 hex digits (base64 also expands to 8 due to padding).

    • An IP address is 4 bytes

      IPv6 exists you know?

      • Yes but OP took the string representation of the IPv4 and base64'd it, I was addressing that part specifically.

        • And I'm addressing your statement that "an IP address is 4 bytes" in specific. I understand their example is IPv4, but you just blatantly said that "An IP address is 4 bytes" when that's not the case for IPv6 which a good chunk of the world is using now (still not a majority though...).

          His code takes the base64 of anything that's returned in both (together) ip and timestamp. So the long string is both values concat'd then encoded. Most of that string is going to be the timestamp...

          Specifically MTEuMjIuMzMuNDQ is 11.22.33.44
          Where ---KIApTdW5kYXksIDI3LUFwci0yMDI1IDE1OjA0OjM5IENFU1QK is the date string Sunday, 27-Apr-2025 15:04:39 CEST.

          While it's still a "bigger" value than it needs to be, it's not like it's the end of the world for an email address. I mean, if we really want to get "fancy" most people don't know that you can just go to an IP address in it's decimal form...

          1.1.1.1 -> 16843009 (http://16843009) No need to encode anything special at all in that case. But that's neither here nor there... Can always make your own with blackjack and hookers of course.

20 comments