• dan1101
    link
    fedilink
    arrow-up
    5
    ·
    11 days ago

    Honestly no idea why they didn’t just do that to begin with.

    • elgordino@fedia.io
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      11 days ago

      Because it’s actually really hard to achieve technically. When ads are served outside the stream you can easily serve different ads to different viewers based on their profiles. When the ads are baked into the stream you can either

      A) Create a whole bunch of different copies of the video asset with different ads baked in and then rotate these on a regular basis. Which would be expensive to update and store and limit the range of adverts that could be served to a particular user.

      B) Dynamically create a stream on the users request, which while possible means standard CDN caching isn’t going to work so there’s a distribution challenge.

      Or some other alternative they’ve come up with. I’d be really interest to know what their approach is here.

      • Solemn@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        3
        ·
        11 days ago

        Look up how HLS (HTTP Live Streaming) works. They just need to generate a personalized playlist for each person which points at things already hosted on CDN, and insert the ads where they want in the literal text file that your video player reads from to serve you the video.

        I don’t know much about it, but it looks like there’s specific tags designed for dynamic ad insertion. Idk if YouTube plans to use them in this case though, if they want it to be undetectable to the client.