Comment on Strings do too many things

• Tramort@programming.dev ⁨9⁩ ⁨months⁩ ago

  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.

  source

  • hansl@lemmy.world ⁨9⁩ ⁨months⁩ ago

    We were discussing validation, not parsing. There’s no parsing in an email. You might give it a type once it passes validation, but an email is just a string with an @ in it (and likely some . because you want at least 1 TLD but even that I’m not sure).

    source
  • Black616Angel@feddit.de ⁨9⁩ ⁨months⁩ ago

    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.

    source
• pkill@programming.dev ⁨9⁩ ⁨months⁩ ago

  fuck any website that requires an account to just READ it’s stupid content and at the same time blocks guerrillamial/10minutemail (looking at you, Glassdoor,I don’t want to get fucking spam just so that I can check approximate salary in a company)

  source

  • hansl@lemmy.world ⁨9⁩ ⁨months⁩ ago

    Sounds like your gripe is with people requiring accounts for reading public content, and not with preventing usage of automated email creation and trying to limit bots on your website.

    source
• ono@lemmy.ca ⁨9⁩ ⁨months⁩ ago

  disallow list of known bad email providers.

  Imagine giving someone your phone number, and having them say you have to get a different one because they don’t like some of the digits in it.

  I have seen this nonsense more times than I care to remember. Please don’t build systems that way.

  If you’re trying to do bot detection of the like, use a different approach. Blacklisting email addresses based on domain or any other pattern does a poor job of it and creates an awful user experience.

  source