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.

      • Redredme@lemmy.worldEnglish
        18·
        11 months ago

        Im with the earlier “yeah… No.”

        Because

        “If people can take case-dependence for passwords”

        They cant now do they ? If they could passwords would be a-okay and there wouldn’t be any need for stickies on monitors, password managers, biometrics, SSO, MFA and passwordless authentication.

        The dumbest idea in computing is assuming everyone is as smart as you.

        They aren’t. Why isn’t *nix any bigger? Here’s your answer. People are stupid.

        Why did IT only finally took off with windows 3.11? because people could understand that. Barely. Most of us where way to dumb for everything which came before.

        Why does ipv6 acception takes so long? Because people are stupid and don’t get it. Nobody really gets hex. So they just stay with what they can read and more or less get. Even the hardest part of ip4, subnetting, has an easy way out: just add 255.255.255.0 in there and it works. Doesnt work? Keep replacing 255 with zeros and eventually it will. Subnetting on ipv6? No idea. Let’s just disable ipv6 on the internal lan and leave everything on ipv4. Zero migration, zero risk, zero training needed.

        Why do so many companies only go half assed into cloud? Because they don’t get it.

        Powershell? Only half, a third even, of the admins truly get it.

        I could go on.

        Succes is build on simplicity.

      • dan@upvote.auEnglish
        12·
        11 months ago

        ‘U’ and ‘u’ are two different symbols. And you have to make such rules for every language a part of your processing logic.

        Unicode has standard rules for case folding, which includes the rules for all languages supported by Unicode. Case-insensitive comparisons in all good programming languages uses this data.

        Note that you can’t simply convert both strings to uppercase or lowercase to compare them, as then you’ll run into the Turkish i problem: https://haacked.com/archive/2012/07/05/turkish-i-problem-and-why-you-should-care.aspx/

        • labsin@sh.itjust.worksEnglish
          4·
          11 months ago

          It’s that capitalization is language dependent, which email addresses shouldn’t be as I hope the rules for France shouldn’t be different than for Dutch. For instance é in Dutch is capitalized as E, but in French it is É. The eszett didn’t even have an official capital before 2017

          In most programming languages, case-insensitive string compare without specifying the culture became deprecated. It should imo only be used for fuzzy searching doubles, which you probably will do with ToUpper for performance reasons, or maybe some UI validation.

          • dan@upvote.auEnglish
            5·
            11 months ago

            For instance é in Dutch is capitalized as E, but in French it is É

            Sure, but we’re just talking about string comparison rules, and Unicode sees all three of those as being equal. For example, a search engine that uses proper case folding rules in its indexer should return results for “entrée” if you search for “entree”, “Čech” if you search for “cech”, etc.

            It should imo only be used for fuzzy searching doubles, which you probably will do with ToUpper

            You can’t just use ToUpper for comparisons due to issues like you mentioned, and the Turkish i problem. You need to do proper case-insensitive comparisons, which is where the Unicode case folding rules are used.

      • Natanael@slrpnk.netEnglish
        4·
        11 months ago

        But then you run into the issue of incredibly trivial impersonation on any email service which doesn’t reserve all variants of registered names