Regex Review By Trust Fall
Description
The image is a cropped GitHub-style pull request diff with a green added-code block at the top and an inline review comment below. The visible code imports Python's `re` module and adds an `email_regex` raw string that appears to match lowercase email addresses with character classes, an optional dot or underscore, an at sign, a word-domain segment, a dot, and a 2-to-3-character suffix. A reviewer comment in the thread says, "i'm gonna trust you with this one," followed by a reply field and a "Resolve conversation" button. The joke is that regular expressions, especially email regexes, often become so dense that code review turns from verification into social trust.
Comments
27Comment deleted
Every email regex review eventually reaches the same approval state: LGTM, pending formal proof by someone else's outage.
Dashes would not work(idk if they are in actual email addresses) Comment deleted
Many things won't work that's awful regex for email Comment deleted
it matches only one _, so email [email protected] won't work Comment deleted
we don't need that many users anyway, come back when you have a NORMAL email Comment deleted
I'm just gonna register on 20minutemail.com email for that Comment deleted
you can always verify on stakO Comment deleted
How to verify email address 1. You don't use regex 2. Just try to send a message. If they registered - great, if not - autodelete account Comment deleted
Lol I can see ddos Comment deleted
Just the same with the valid email addresses? Comment deleted
Nvm I am on the go. I was already distracted by my email not working with that regex Comment deleted
Or do you mean I should remove autodeletion? Comment deleted
I usually use [email protected], so I know who sent me spam or sold/leaked my data (you can put anything after "+" in Gmail [email protected] and [email protected] are same mailboxes) And it won't work here because of + Comment deleted
Nice hint Going to try this Comment deleted
tnx Comment deleted
Thanks! Comment deleted
Thankyou sir. That’s cool! Comment deleted
Thanks. What resources already leaked your data? Comment deleted
this is an extremely stupid regex. Would not work for for [email protected], or for [email protected]... Comment deleted
Also this regex doesnt work for something like [email protected] Comment deleted
dot is optional, btw. 2-3 for domain zone is obsolete, so... The one and only way to check if that's a valid email address is that there have to be something before and after @. Let's say .+@.+ (valid != existing) Comment deleted
RFC 822 https://stackoverflow.com/questions/20771794/mailrfc822address-regex looks much better Comment deleted
[email protected] Comment deleted
And my password is nicknameyear /s Comment deleted
with space and slash-s appended? Comment deleted
Nope just everything together Comment deleted
If you had some issue and solved this issue by regex, so now you have two issues Comment deleted