Mac@programming.dev to Programming@programming.dev · 7 months agoStrings do too many thingsbuttondown.emailexternal-linkmessage-square10fedilinkarrow-up10arrow-down10
arrow-up10arrow-down1external-linkStrings do too many thingsbuttondown.emailMac@programming.dev to Programming@programming.dev · 7 months agomessage-square10fedilink
minus-squarehansl@lemmy.worldlinkfedilinkarrow-up0·7 months agoThere are also cases where you want to have a disallow list of known bad email providers. That’s also part of the parsing and validating.
minus-squareTramort@programming.devlinkfedilinkarrow-up0·7 months agoIt’s a valid need, but a domain blacklist isn’t part of email parsing and if you conflate the two inside your program then you’re mixing concerns. Why is the domain blacklist even in your program? It should be a user configurable file or a list of domains in the database.
minus-squareBlack616Angel@feddit.delinkfedilinkarrow-up0·7 months agoYou are right in that it isn’t (or shouldn’t be) part of the parsing, but the program has to check the blacklist even if it’s in a database.
There are also cases where you want to have a disallow list of known bad email providers. That’s also part of the parsing and validating.
It’s a valid need, but a domain blacklist isn’t part of email parsing and if you conflate the two inside your program then you’re mixing concerns.
Why is the domain blacklist even in your program? It should be a user configurable file or a list of domains in the database.
You are right in that it isn’t (or shouldn’t be) part of the parsing, but the program has to check the blacklist even if it’s in a database.