61–70 of 102 posts
Earlier quoted context omitted.
Netflix does not encode content per-user, it's all static content on CDNs
A/B watermarking is about static content on CDNs... For every segment in a video there will be two versions. Every user will get a unique sequence of segments served to them.
Earlier quoted context omitted.
A/B watermarking is about static content on CDNs... For every segment in a video there will be two versions. Every user will get a unique sequence of segments served to them.
Netflix puts flat MP4s on the CDN, the segments all reference different offsets within the MP4.
THIS EXTENSION DOES NOT WORK!
let me put it another way:
THIS EXTENSION DOES NOTHING USEFUL!
The author did not reverse engineer anything. He simply asked Claude Code to make this without testing or verifying any of the outputs.
The author did not check if the extension actually works. He simply asked Claude Code to make this without testing or verifying any of the outputs.
Other commenters in this thread have noted that this extension cannot do what it claims. [1] The author simply asked Claude Code to make this without testing or verifying any of the outputs.
Thanks for listening to my ted talk.
Earlier quoted context omitted.
To what extent does this watermarking survive transcoding? Would not transcoding multiple times possibly affect it? > They also use a traitor tracing scheme (Tardos codes) such that if multiple pirates get together to try and remove the watermark they will fail, you would need an unreasonably large number of pirates to succeed for some length of time. Why?
> To what extent does this watermarking survive transcoding? Would not transcoding multiple times possibly affect it? They are designed to survive being recorded by a phone at an angle. The embedding is only 1-bit per segment which can be multiple megabytes. > Why? Tardos codes scale as the square of the number of traitors times a constant. For example, a movie would typically have 2000 segments -> 2000 bits of encod…
Earlier quoted context omitted.
Netflix puts flat MP4s on the CDN, the segments all reference different offsets within the MP4.
Have you inspected the contents of their CDN servers? Because assembling an mp4 on the fly from segments is not difficult. Especially if they condition them to have identical sizes.
Earlier quoted context omitted.
Have you inspected the contents of their CDN servers? Because assembling an mp4 on the fly from segments is not difficult. Especially if they condition them to have identical sizes.
I have indeed inspected the contents of their CDN servers. The URLs have an auth token in them but you can edit the range parameters to grab the whole mp4 in one go without invalidating the auth.
Also, I assume the file in question is 4K content. Don't know about how they treat other types.
Hello HN, I have an important thing to point out: THIS EXTENSION DOES NOT WORK! let me put it another way: THIS EXTENSION DOES NOTHING USEFUL! The author did not reverse engineer anything. He simply asked Claude Code to make this without testing or verifying any of the outputs. The author did not check if the extension actually works. He simply asked Claude Code to make this without testing or verifying any of the ou…
Earlier quoted context omitted.
Netflix does not encode content per-user, it's all static content on CDNs
A/B watermarking is about static content on CDNs... For every segment in a video there will be two versions. Every user will get a unique sequence of segments served to them.
If a single video has say 100 segments, you get more than enough unique combinations to guarantee uniqueness. There would of course have to be a mapping between user/device ID and segment order.
Earlier quoted context omitted.
Netflix does charge more for 4k, so they simply pass along the cost: https://help.netflix.com/en/node/24926
Netflix still saves money when someone watches in a lower resolution.