this post was submitted on 13 Jun 2024
605 points (96.5% liked)

Technology

57389 readers
5853 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Lemminary@lemmy.world 28 points 2 months ago (2 children)

Feedback across the Firefox and YouTube subreddits highlighted that it could break timestamped video links and chapter markers. However, YouTube knows the length of the ads it would inject, and can offset subsequent timestamps suitably.

The move also adds a layer of unnecessary complexity in saving Premium viewers from these ads. If they are added server-side, the YouTube client would have to auto-skip them for Premium members, but that also means ad segment info will be relayed to the client, opening up a window of opportunity for ad blockers to use the same information meant for Premium subscribers and skip injected ads automatically.

It sounds like there's a silver lining after all.

[–] 4am@lemm.ee 25 points 2 months ago (1 children)

The ads won’t be baked in beforehand, they’ll be injected into the stream in real time. Videos are broken into chunks and sent over HTTP, they’ll just put ad chunks in during playback. There is no need to re-encode anything. If you deep link to a timestamp, the video just starts from that timestamp as normal. If you are a Premium user, the server just never injects the ads.

But you are correct that the client needs to be aware that ads are happening, so they can be indicated on screen, and so click-throughs are activated.

This is why Chrome went to Manifest v3 - so you can’t have any code looking for ad signals running on the page to try to counter it.

[–] Lemminary@lemmy.world 6 points 2 months ago

But you are correct

That's what the article says, not me! lol

[–] Tamo240@programming.dev 8 points 2 months ago* (last edited 2 months ago)

Surely at the server side it knows the premium status of the user it is supplying the video to, so just wouldn't insert the ads? I don't see why that would need to be client side.