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.com
    link
    fedilink
    English
    arrow-up
    22
    ·
    11 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.world
      link
      fedilink
      English
      arrow-up
      11
      ·
      11 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.

    • drathvedro@lemm.ee
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 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.