• illi@lemm.ee
    link
    fedilink
    English
    arrow-up
    7
    ·
    16 days ago

    From what I read, this also breaks sponsorblock - as the ads are part of the video, it moves the time stamps of the video so it makes it not correct. The ads will also change I imagine so idk if sponsorblock will be a solution.

    • jayknight@lemmy.ml
      link
      fedilink
      English
      arrow-up
      12
      ·
      16 days ago

      So videos that reference timestamps in their own video won’t work? And comments that reference a timestamp won’t work?

        • gila@lemm.ee
          link
          fedilink
          English
          arrow-up
          4
          ·
          16 days ago

          Wouldn’t that need to be done via some kind of API for cross-platform compatibility? An API which could be exploited to detect ad segments?

            • gila@lemm.ee
              link
              fedilink
              English
              arrow-up
              2
              ·
              16 days ago

              So that the timestamp adjustment can be propagated via uploader or user comments across YouTube clients on all platforms… i.e. to avoid having to hardcode each adjustment for each ad on each video on every client

              • relevants@feddit.de
                link
                fedilink
                arrow-up
                2
                ·
                15 days ago

                Why couldn’t they just serve the comments to each client with the ad-adjusted timestamps already? The only thing the client has to request then is the comment page it wants to load, and some unique ID for which the backend remembers which ad version it’s associated with.