Click a link and need to go back 10x to get back. Yes, I enjoy the footballs.

  • bitwolf@lemmy.one
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    You can right click (long press on mobile) to skip back to the page that took you there

    • intensely_human@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      That’s what OP has done; that’s what we’re seeing in this screenshot.

      The back button is highlighted. This list is the list of options OP gets when he right clicks the back button.

  • Eiri@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I’ve always wondered. Is there really a benefit to a ton of redirects like that? Like, do they gain anything by making it harder to back out?

    Or is it just extremely incompetent website programming?

    • prole@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      I always just assumed it was a form of “dark pattern” meant to try to stop people from leaving their website once they’ve entered (e.g., coming from a different site, you can’t just hit backspace or click back to immediately exit their site. You’re stuck now).

      • Eiri@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        I think that’s right for a website where you accidentally clicked an ad and now it’s trying to convince you you have a virus and you need to download their virus to remove it. Or maybe for an ad pop-up where annoying you might increase the chances that the content makes it into your brain.

        But for a news website i have trouble seeing the logic.

          • Eiri@lemmy.ca
            link
            fedilink
            English
            arrow-up
            0
            ·
            4 months ago

            I’d have expected ad providers to catch on pretty quickly that there’s cheating involved, no?

            • Krauerking@lemy.lol
              link
              fedilink
              English
              arrow-up
              0
              ·
              4 months ago

              Nope. They just hear back about number of views and how it influences the shoppers and brags about how it works.

              I honestly think it’s mostly the idea of advertising that keeps it running as an industry.

              Like Facebook juicing their video viewership and recent news about Google using off screen ads in their views and impressions numbers.

  • terminhell@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    Not sure about that site specifically, but others that’s done it to me was easy to get around. Most of them are thwarted with basically double clicking the back button.

    • intensely_human@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      As the screenshot illustrates, the redirects have been repeated many times to thwart that strategy.

  • The Pantser@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    This could easily be fixed by the browsers but they don’t. Sure wish these back button tricks would stop. Especially news sites try to keep you from getting back to your search and makes your page refresh over and over. I wonder if that behavior counts as hits to their advertisers.

    • ilinamorato@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      I don’t know about “easily.” replaceState() is actually intended to make single-page apps easier to use, by allowing you to use your back button as expected even when you’re staying on the same URL the entire time.

      Likewise, single-page apps are intended to be faster and more efficient than downloading a new static page that’s 99.9% identical to the old one every time you change something.

      Fixing this bad experience would eliminate the legitimate uses of replaceState().

      Now, what they could do is track your browser history “canonically” and fork it off whenever Javascript alters its state, and then allow you to use a keyboard shortcut (Alt + Back, perhaps?) to go to the “canonical” previous item in history instead of to the “forked” previous item.

      • deejay4am@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        Pop a window open with a your app in it (with the user’s permission) without a back button if you want that.

        A web page should be a document, not an experience.

        • ilinamorato@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          That would absolutely make everything worse, no question; the web should be more integrated, not less. We shouldn’t incentivize even more companies to silo off their content into apps.

          • ggppjj@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            4 months ago

            I think the word ‘app’ was being used in place of ‘webapp’ there, which is the general target audience for this feature.

            • ilinamorato@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              4 months ago

              Yes, I think you’re correct, but using browsers to coerce the web back into static documents will result in companies creating their own apps so that they can continue to deliver experiences. And the past 10+ years has shown that users will absolutely follow them.

      • SplashJackson@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        I can handle life without the legitimate use case if it means no more clickjacking bs from companies that should know better

        • ilinamorato@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          I’d prefer not to let the bad actors dictate browser design.

          “Let’s get rid of images since companies can use images to spoof browserchrome elements.”

          “Let’s get rid of text since scammers can pretend to be sending messages from the computer’s operating system.”

          “Let’s get rid of email since phishing exists.”

          Nah. We can do some stuff (like the aforementioned forked history) to ameliorate the problem, and if it’s well-known enough, companies won’t find it necessary anymore. Heck, browsers like Firefox would probably even let you select Canonical Back as the default Back Button behavior, and then you can have the web the way you want it (like people who disable Javascript).

          • ggppjj@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            4 months ago

            I’m frustrated that removing bad functionality is being treated as a slippery slope with obviously bad and impossible jokes as the examples chosen.

            I see a bad feature being abused, and I don’t see the removal of that bad feature as a dangerous path to getting rid of email. I don’t ascribe the same weight that you seem to towards precedent in this matter.

            • ilinamorato@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              4 months ago

              I’ve been working in full stack for long enough to know that history manipulation is as much a part of the modern web as images and email. I’m not trying to be flippant, that’s just the state of the modern web. Single-page apps are here, and that’s a good thing. They’re being used badly, and that’s endemic to all features. So no, history manipulation is not “bad functionality,” though I admit it’s not fully baked in its current implementation.

              • ggppjj@lemmy.world
                link
                fedilink
                English
                arrow-up
                0
                ·
                4 months ago

                I accept that it’s how things are, I just personally feel as though the only way this feature could ever work as it does now is with the implementation it has now, and that the convenience of single page webapps that use history manipulation is not worth the insane annoyance of helping my grandma get out of websites that tell her that she has been hacked by the FBI.

          • gwen@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            0
            ·
            4 months ago

            like people who disable Javascript).

            i do that, and i found that a TON of microsoft & bank/work websites just refuse to do anything without it. i love the modern internet /s

    • Akasazh@feddit.nl
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      What helps with this is clicking links with mousewheeldown, I automatically opens in a new tab. Also MWD on the tab label will close it, so you don’t have to aim for the ‘x’.

      A mouse with thum buttons is really handy as they do foreward and back, double clicking that gets you out of the issue caused in op

  • foggy@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    4 months ago

    Three things.

    1. Yes. Sometimes this is malice. Sometimes this is an attempt to drive impressions and page views.

    2. This can also be caused by poorly configured web applications that update in real time. If, say, some sports website is giving you real-time data about the game as it progresses, a poorly configured web application might be creating a dynamic URL for every change. When you access the older page, it will be instructed to take you to the most recent data, so pressing back is taking you to old data on that page, and then immediately realizing that data is old so refreshing it with the most relevant data.

    3. This is a super common misconfiguration in single page web applications. Domain.com will take you to an application that renders at domain.com/en-us/home. Pressing back takes you to domain.com, and guess what happens next?

    This is basically 99.99% of these cases. I would say if it isn’t on some shitty news site with 1000 ads that somehow sneak by AdBlock and UBlok Origin, it’s case 1. Otherwise, it’s case 2 or 3.

    The picture instance is either case 1 or 2.

    • FuglyDuck@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Any website managed/developed by someone certified in the last decade or more knows not to do that.

      It’s absolutely malicious, both to drive SRO and to keep “accidental” clicks from backing out so quickly

      • mrvictory1@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        4 months ago

        MS makes a redirect to log you in, you can hit back button twice to escape. Bad design but not malice.

    • ajikeshi@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      and neither case provides a service in a state that should be exposed to the outside. Either due to malice or incompetence.

  • katy ✨@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    microsoft does this with their community support/forums/whatever and it’s annoying when you’re trying to look up a problem in google. :///

    • Blackmist@feddit.uk
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Only the first time you visit in a while though.

      I think it’s taking you away to a login page, logging you in, then bringing you back.

      I can see the point if you were going to ask or answer a question, but 99% of the time you just want to see how somebody else didn’t get their problem solved by some random Indian guy who people assume works for Microsoft, who think the solution to everything is running “sfc /scannow” which has replaced chkdsk as the command most likely to take a long time, do nothing, and make the question asker go away without a solution to their problem.