Transcript

A tumblr post saying "i really like this thing where websites will have separate “log in” & “sign up” buttons and if you click “log in” it takes you to a sign-up screen anyway so you have to click “i already have an account” and then it will ask if you want to sign in with your facebook account or with instagram or linkedin or deviantart or whatever, and if you choose “username & password” it asks if you want to put in your username or use your thumbprint, and once you put your username & password it emails you a confirmation code, and once you put in the code it says “do you want to give us your phone number for future sign-ins? do you want to sign up for facial recognition? do you want to give us your bones? give us your fucking bones?”

  • jaupsinluggies@feddit.uk
    link
    fedilink
    English
    arrow-up
    17
    ·
    24 hours ago

    I was confused recently at a border post marked “Passport control”. I had it ready, but the guard asked for my driving licence. While I was fishing for that he breathalysed me, which came back clean so he said I could go - without having seen either my passport or driving licence.

  • LiveLM@lemmy.zip
    link
    fedilink
    English
    arrow-up
    66
    ·
    edit-2
    1 day ago

    And whoever came up with the idea of putting email on one page and password on another: You suck.
    I can never get my password manager to handle that proper. WTF is even the point?

    • azertyfun@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 hours ago

      Usually it’s because some chucklefuck put SSO in the requirements so now everyone has to suffer so that SSO users get their redirect before being shown a password field.

      Sometimes though it’s an absolutely braindead web designer who definitely doesn’t have SSO as a requirement but has no idea what he’s doing and is just doing the mr-bean-cheating-on-a-test.gif and copying their Microsoft login form.

    • mic_check_one_two@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      23
      ·
      edit-2
      1 day ago

      I came to the comments to post this exact complaint. I’m sure it’s considered more secure somehow, (maybe to prevent autofill attacks?) but at least code your fields properly so my password manager can auto detect the username field.

      Also, phone number/ZIP code fields that pull up the full keyboard on mobile, instead of just the number pad. There’s no reason to show the entire keyboard, and phones have the ability to detect what kind of input the field wants… But website devs don’t bother coding their fields properly for numbers only, so the phone pulls up the full keyboard by default.

      Lastly, 2FA fields that break paste. Like when it’s asking for a 6-digit TOTP code, and the field is actually broken up into two 3-digit fields instead.

      • Dunstabzugshaubitze@feddit.org
        link
        fedilink
        English
        arrow-up
        14
        ·
        1 day ago

        countries with alphanumerical postal codes exist, so unless you are 100% sure, that your service won’t be used by someone from such a country, you’d better allow alphanumerical inputs in your postal code field. Addresses in general are tricky, because they work different across the globe, for example house numbers are not a thing everywhere, hell i am not sure if streetnames are a thing everywhere.

      • SimpleMachine@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 day ago

        Feels like a security issue to me. You could put in literally anyone’s email address on a site that does this and immediately know if they have an account there or not. Even if you don’t know their password, you know something new about that person.

        I feel you on all these other ones too. There’s a lot of UI/UX designers out there that need to be barred from that field forever.

      • cactusupyourbutt@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 day ago

        its because of SSO. if your company signs up for something that implements SSO then the tool will need your mail, recognizes that you‘re from company X, and forward you to yoir companys login page so ot can get an auth token

        • saigot@lemmy.ca
          link
          fedilink
          English
          arrow-up
          2
          ·
          21 hours ago

          Github doesn’t use two screen login but also still works with sso.

        • osugi_sakae@midwest.social
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 day ago

          Yes, this, but I don’t think just for organization’s login pages. The email may also lead to a google sign in (for example) or some other single sign on (SSO). The site you are on needs to know the email to decide what to show next to continue the log in process.

          That said, web devs should be coding the fields correctly.

      • JackbyDev@programming.dev
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 day ago

        Auto fill attacks is a weird way of saying password managers. You know. Those things that make it easier to use good password practices and be more secure.

        • mic_check_one_two@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 day ago

          I mean, there’s a reason browsers moved towards asking to autofill. Back when browsers would just do it automatically, there were malicious pages/ads that would hide fake username+password fields offscreen. So when the ad loaded, the browser would try to be helpful and would autofill the info. Then the ad would simply capture the autofilled info, and now your account is compromised.

          Autofill attacks were so awful because the browser automatically did it without asking first. It was literally a zero-click drive-by attack that nabbed your info without any prompting or alerts on the user’s end. So to try and combat this, browsers moved towards requiring a prompt.

          Tangentially, malicious ads then started using clipboard attacks instead. The ad would simply request your clipboard data, because there was a very good chance that it was your password. That’s why browsers stopped allowing sites to request clipboard data at all, and now it requires the user to actually push the data via a Ctrl+v instead; Anyone who has used Google Docs/Google Sheets will be able to tell you that Right Click>Paste doesn’t work, and it’s because the site isn’t allowed to request access to your system’s clipboard.

          • JackbyDev@programming.dev
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 day ago

            That’s all very interesting and insightful, but I don’t see how a site putting username and password entry on separate screens helps mitigate any of this, unless they’re doing something like showing ads on the page that asks for the username but not the one that asks for the password? I typically use ad blockers so I genuinely don’t know what’s standard. My gut feeling would but they don’t show ads on those pages at all. Apart from sites that have username and password boxes on the main page. But that’s still no reason to split the password from the username if both are on a dedicated page with no ads. I don’t see how it would prevent against fake password entry boxes either. Most of those sound like things the browser would ultimately need to mitigate against since any site could be compromised. Obviously sites have some role in it too.

      • AppleTea@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 day ago

        KeePassXC lets you edit the auto-type for each individual password, so you can have it go

        {USERNAME} {ENTER} {DELAY X} {PASSWORD} {ENTER}

        x would be a number of milliseconds you may need for the next page to load in

  • untorquer@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    edit-2
    1 day ago

    Shout out to

    <<Login>>

    Uname:

    Pword:

    Or sign in with [Gargle] [Equis] [Fightbook]

    Don’t have an account? [Sign up here!]

    • Mniot@programming.dev
      link
      fedilink
      English
      arrow-up
      6
      ·
      22 hours ago

      It’s shitty, but it’s not “enshittification”.

      Doctorow’s explanation goes

      Here is how platforms die: first, they are good to their users; then they abuse their users to make things better for their business customers; finally, they abuse those business customers to claw back all the value for themselves. Then, they die. I call this enshittification

      What the OP describes is just obnoxious design. To be enshittification it should be a change from better UX to worse and the change should be an attempt by the site to grab some extra cash.

      Twitter requiring an account to see replies to a tweet is an example–they’re trying to juice their user-count.

  • salacious_coaster@infosec.pub
    link
    fedilink
    English
    arrow-up
    73
    ·
    2 days ago

    In all seriousness, I’m hating this latest trend where you click the “login” button (page refresh 1) and they ask if you want to use a one time code or password, and I use a password manager like a functioning adult, so I click “password” (page refresh 2, could have already been logged in by now) and THEN I get to input my password (page refresh 3) and then they’re like “y’know what, we’re gonna send you a one-time code anyway” (page refresh 4) so I have to retrieve that and finally get to login on page FIVE.

    We used to be a proper Internet.

    • colin@lemmy.uninsane.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      15 hours ago

      don’t forget the “install our app to make the next login faster” interstitial after you press “login”. can you really claim they don’t care about how painful their login process is when they’ve gone out of their way like that to provide you with a less painful option??

    • Norah (pup/it/she)@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      48
      ·
      2 days ago

      Then the chucklefucks manage to have the worst backend security imaginable and all your data gets breached in a leak anyway but they make their security look really impressive to customers so for six glorious months they created Shareholder Value and the c-suite already took their golden parachutes.

      • Randelung@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        1 day ago

        Most grievous mistake designers make is assume the attacker will take the front door and pick the lock instead of breaking a window, walking though the hole in the fence and taking the side door or just walk though the other side, where literally the whole wall is missing.

        But at least you have a padlock, a deadbolt, a high security door lock, a chain link, a nest AND a ring camera,

  • Rose Thorne(She/Her)@lemmy.zip
    link
    fedilink
    English
    arrow-up
    55
    ·
    2 days ago

    Don’t trust any website that asks for your bones.

    It’s secretly run by the rambling gambling skeletons. No one wants to play euchre anymore, so they had to take a different angle.

  • snooggums@lemmy.world
    link
    fedilink
    English
    arrow-up
    36
    ·
    2 days ago

    "i really like this thing where websites will have separate “log in” & “sign up” buttons and if you click “log in” it takes you to a sign-up screen anyway so you have to click “i already have an account

    I used to wonder if I clicked the wrong thing but this is so fucking common that I just assume the website is designed by idiots who can’t use a single button for the same thing.

    • SpaceNoodle@lemmy.world
      link
      fedilink
      English
      arrow-up
      18
      ·
      2 days ago

      The PM insists that there be separate buttons labeled thusly and that they do the exact same thing

      • atomicbocks@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 days ago

        In my experience it’s been because the login app was done by a different team than this web app and this PM promised that they could save time by reusing the old code.

      • snooggums@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        2 days ago

        If the PM gets to make design decisions then that counts.

        I know why it ends up this way, because the stupid people who complain the most don’t know if they have an account or not, but the workflow that has become common is the must frustrating one for users who do know what they are doing.

  • osugi_sakae@midwest.social
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 day ago

    Not as bad as the log in button taking you to the sign up page, but my local library’s site has a “log in” button that, when you click it, brings up “log in” and “sign up” options on a CSS drop down (though I’m sure they use javascript, just because why do it the easy, safe way). You literally have to click “log in” twice to get to the log in page.

  • infinitesunrise@slrpnk.net
    link
    fedilink
    English
    arrow-up
    18
    ·
    2 days ago

    Also shout out to front end js libraries that hijack and discard familiar default page rendering behavior in favor of asserting their own arbitrary, untrustworthy, and inferior render behaviors that break completely outside of chrome browser or with any extensions running, gotta be my least favorite gender.

    Like how so many sites just fuckin come to a dead stop and reload completely if you click literally anything because the developer didn’t follow React design philosophy perfectly. Thanks a million, Facebook, so cool so cool.

  • Lvxferre [he/him]@mander.xyz
    link
    fedilink
    English
    arrow-up
    20
    ·
    2 days ago

    do you want to give us your phone number for future sign-ins?

    Urgh, that’s probably the worst part.

    I don’t mind mail-based 2FA. However, since I see “random sites have your phone number” as a bigger threat than “skript kiddo might hack your password”, if the 2FA must use my phone number, I’ll genuinely think if I really need an account in that site, and probably give up.

    • kautau@lemmy.world
      link
      fedilink
      English
      arrow-up
      16
      ·
      2 days ago

      All sites should support TOTP, fuck email/sms OTPs, and especially fuck sites that think being “passwordless” but sending a code to my email is secure.

  • cogitase@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    20
    ·
    2 days ago

    You’re not actually giving the website access to your fingerprint or other biometric information by doing that. That’s all handled on your device which then sends a verification message.