417

Mo Validation Mo Problems (lemmy.world)

submitted 1 week ago* (last edited 1 week ago) by qaz@lemmy.world to c/programmer_humor@programming.dev

68 comments fedilink hide all child comments

...

you are viewing a single comment's thread
view the rest of the comments

[-] elvith@feddit.org 206 points 1 week ago* (last edited 1 week ago)

A plus sign? That's nothing, LOL

Quote:

If you disagree, or have any other comments, feel free to email me at
'*+-/=?^_`{|}~#$@[IPv6:2602:f977:800:0:e276:63ff:fe72:3900]
-- if your mail client lets you, that is.

[-] mormegil@programming.dev 4 points 5 days ago

Because of one smartass customer who insisted on doing exact RFC 822 validation, I implemented exactly that. And yes,

zKcknV|NGv.lI66vR#@X`QcRK4K.R`?NpA.Gc2Kqzue9.%&nb1kGWp/./#Och$RQv

is one of the test cases for a valid addr-spec. See (or generate) some others at https://github.com/mormegil-cz/rfcemailvalidator

[-] boonhet@sopuli.xyz 48 points 1 week ago

I like this issue in the form of a quiz

[-] mech@feddit.org 19 points 1 week ago* (last edited 1 week ago)

TIL:
🫱@🫲
is a valid e-mail address.

[-] erer@lemmy.zip 4 points 1 week ago

I dont know if it's just me, but this comment is breaking the rendering of Voyager

[-] elvith@feddit.org 3 points 1 week ago

I needed to use a code block for that address as several apps had a problem when I tested escaping the back ticks in the address for the inline code. Not sure if you mean that as it renders in it's own line or if anything else is broken