I also reached out to them on Twitter but they directed me to this form. I followed up with them on Twitter with what happened in this screenshot but they are now ignoring me.

  • ShunkW@lemmy.worldEnglish
    82·
    11 months ago

    Let’s see your regex pattern that covers every possible valid email address and rejects all invalid then. It’s not remotely as easy as you’re making it out to be.

    Not saying this isn’t a shitty pattern, but you can’t make a claim like that.

    • laurelraven@lemmy.blahaj.zoneEnglish
      41·
      11 months ago

      What claim, that I probably could? I didn’t say anything at all about it being easy, it would be a pain in the ass and involve a lot of checking the RFC, but I could probably make one that accurately represents the spec if I wanted to take the time, and even then I’m not exactly confident I would hit every edge case.

      But why would I go to that hassle when there are well designed and vetted ones available?

      I believe you missed the point I was making

      • nybble41@programming.devEnglish
        2·
        11 months ago

        The full email address syntax described in the RFC cannot be precisely matched with a mere regular expression due to the support for nested comments. The need to track arbitrarily deep nesting state makes it a non-regular language.

        If you remove the comments first the remainder can be parsed with a very complex regex, but it will be about a kilobyte long.