• LoafyLemon
    link
    fedilink
    105
    edit-2
    1 year ago

    You absolutely can tell what’s happening by reading the source code. They are using a listener and a delay for when ontimeupdate promise is not met, which timeouts the entire connection for 5 full seconds.

    https://pastebin.com/TqjzbqQE

    • Schwim Dandy
      link
      fedilink
      181 year ago

      I’m sorry but I don’t see how that check is browser-specific. Is that part happening on the browser side?

      • @PoliticalAgitator@lemm.ee
        link
        fedilink
        281 year ago

        They don’t need to put incriminating “if Firefox” statements in their code – the initial page request would have included the user agent and it would be trivial to serve different JavaScript based on what it said.

        • @phx@lemmy.ca
          link
          fedilink
          271 year ago

          Easy enough to test though. Load the page with a UA changer and see if it still shows up when Firefox pretends to be Chrome

          • @TastehWaffleZ@lemmy.world
            link
            fedilink
            28
            edit-2
            1 year ago

            The video in the linked article does just that. The page takes 5 seconds to load the video, the user changes the UA, they refresh the page and suddenly the video loads instantly. I would have liked to see them change the UA back to Firefox to prove it’s not some weird caching issue though

          • @PoliticalAgitator@lemm.ee
            link
            fedilink
            11 year ago

            I don’t know, nor am I speculating. The person I was replying to said they didn’t see a browser check in the code, which isn’t enough to dismiss it.

    • Karyoplasma
      link
      fedilink
      91 year ago

      Well, at least I learned that javascript understands exponential notation. I never even bothered to try that lol