Edit: Replies to this thread indicate this is not fully correct as it exists on all browsers; and is likely an ad thing.

  • Echo Dot
    link
    fedilink
    6010 months ago

    Whoever posted this is not a programmer. Does no conditional on that code so it would run on every browser on every session so where’s the check for Firefox?

    Unless they are claiming that it is injected at runtime. But that’s easily provable/disprovable with agent spoofing.

    • @[email protected]
      link
      fedilink
      English
      33
      edit-2
      10 months ago

      In the demo I saw they did an agent spoofing to Chrome and the delay went away, but it didn’t look very extensively tested. As others said, the disappearance on reload could easily be because they thought he was returning to the page and had already seen the ad/been punished for not seeing the ad and so something ad-related disappeared instead.

      • idunnololz
        link
        1710 months ago

        Iirc the thing is it loads a different js file when it detects chrome which doesn’t have the 5s delay. The reasoning is this is part of some anti adblocker code and chrome didn’t need the extra logic.

        • Echo Dot
          link
          fedilink
          110 months ago

          So it’s got nothing to do with Firefox it’s to do with preventing and blocking so it’ll happen on Chrome as well.

          • idunnololz
            link
            410 months ago

            Well chrome doesn’t need the 5s delay.

            • Echo Dot
              link
              fedilink
              410 months ago

              Chrome doesn’t need a 5 second delay to implement ad blocking, or Chrome doesn’t need a five second delay because it’s Chrome?

              Does an important difference here because one is anti-competitive and the other isn’t.