this post was submitted on 23 Sep 2024
552 points (97.3% liked)
Technology
58451 readers
5673 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- 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
view the rest of the comments
Why would that be the case? The player can simply be locked into ad mode till it gets the cue from the server all of the ads have been streamed. Only then will the player unlock. When watching what amounts to a video stream, this doesn't have to be handled clientside.
Well the player and its controls are client side.
I'm not talking about the player or the controls being server-side. I'm talking about the player being locked into a streaming mode where it does nothing but stream the ads. After the ads are streamed, the player returns to normal video mode and the server sends the actual video data.
This means no metadata about the ads are required on the player side about the ads.
Sure you can hack the player into not being locked during the streaming of the ads. But that won't get you very far, since it's a live stream. You can't skip forward, because the data isn't sent yet. You can skip backwards if you'd like, with what's in the current buffer, but why would you want to? You can have the player not display the ads, but that means staring at a blank screen till the ads are over. And that's always the case, one can simply walk away during the ads.
Technically I can think of several ways to implement this, without the client having meta data about the ads. And with little to none ways of getting around the ads. Once the video starts it's business as usual, so it doesn't impact regular viewing.
So you would need buffer barrieres essentially.
Still user watches video. Ad avoidance skips forward to buffer barrier to play ad in the background. Streamed ad is thrown away and new buffer data is received. User does not notice if the video is long enough.
In this case the buffer limit is the metadata.
Yeah I'm thinking of a system like this:
A user opens a session to watch a video, the user is assigned a token to watch the requested video. When the user isn't a premium subscriber and the video is monetized the token is used to enforce ads. To get video data from the server, the user needs to supply the token. That token contains a "credit" with how many seconds (or whatever they use internally) the user can watch for that video. In order to get seconds credited to the token, the user needs to stream ad content to their player. New ad content is only available to stream, once the number of seconds they were credited have been elapsed.
One way to get around this is to have something in the background "watch" the video for you, invisible, including the ads. Then records the video data, so it's available for you to watch without ads. But it would be easy to rate limit the number of tokens a user can have. There's ways to get around that as well. But this seems to me well beyond what a simple browser plugin can do, this would require a dedicated client.
The idea is to make it harder for users to get around the ads, so they'll watch them instead of looking for a way to block ads. In the end there isn't anything to be done, users can get around the ads. Big streaming services use DRM and everything and their content gets ripped and shared. With YouTube it would be easy for someone to have a Premium account, rip the vids and share them. But by putting up a barrier, people watch the ads. YouTube doesn't care if a percentage of users doesn't watch the ads, as long as most of them do.
My point was, there's ways to implement the ads without sending metadata about the ads to the client.