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.

  • Trailblazing Braille Taser@lemmy.dbzer0.comEnglish
    23·
    10 months ago

    Even that would be technically incorrect. I believe you could put an A record on a TLD if you wanted. In theory, my email could be me@example.

    Another hole to poke in the single dot regex: I could put in fake@com. with a dot trailing after the TLD, which would satisfy “dot after @” but is not an address to my knowledge.

    • douglasg14b@lemmy.worldEnglish
      12·
      10 months ago

      And this sort of thing is exactly how you end up with bad regex that invalidates valid emails.

      The point isn’t to invalidate all bad emails. It’s to sort out most of them.

      • WetBeardHairsEnglish
        1·
        10 months ago

        You can’t really depend on everyone’s shitty regex skills to be valid or that they are smart enough to just send a fucking email to validate an address - so instead just pick an email which will actually work with those shitty regexes. You can’t fix the world. But you may still want to order a burrito.

    • drathvedro@lemm.eeEnglish
      5·
      10 months ago

      Something something http://[2607:f8b0:4004:c09::8a] and http://3627734062 are valid url’s without a dot, and are probably valid for emails too, but I’m too lazy to actually verify that.