you are viewing a single comment's thread
view the rest of the comments
[–] [S] 4 points 1 month ago (6 children)
  • [–] 7 points 1 month ago (2 children)

    Holy overengineering, Batman. IP addresses of all things are trivially parseable into fixed-length byte sequences. Just do that and use a search tree. Or, IDK; this is an extremely solved problem, there are probably even better solutions out there -- but I promise you text regex is involved in none of the good ones.

    Even for actual string matching, any decent regex engine will compile and optimise an alternation a|b|c|... better than this text wrangling will. Unless you have actual benchmarks showing this gives you an advantage with the engine you're using, you're just introducing complexity for no gain.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 month ago (2 children)

    It's called "allowlist" and "denylist" nowadays as it's easier to understand for non-native speakers and not racist.

    I feel like there's an easier and faster way to match IP addresses than regex, e.g. the search tree apparia suggested. At least use bytes to match 😄

  • source
  • parent
  • hideshow 2 child comments
  • [–] [S] 2 points 1 month ago* (1 child)

    The term's connection with racism, as well as the value in avoiding its use has been disputed.

    https://en.wikipedia.org/wiki/Blacklist_%28computing%29#Controversy_over_terminology

    (See the section that follows for more context.)

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 month ago

    Yes, but does it really hurt you to make your software more accessible?

    What good arguments do you have for the term blacklist?

    "Denylist" is easier to understand and doesn't spark discussions. Nobody will be offended, whether it's technically correct to be offended or not.

    I'm not a person of colour but your answer still insults me, because it's so tone deaf.

  • source
  • parent