Or maybe it's a trial run for HBO to gauge what viewers think of binge watching.
Game of Thrones leak and watermark: a stupid tracking system
141–150 of 286 posts
Re: Game of Thrones leak and watermark: a stupid tracking system
#142Earlier quoted context omitted.
Or, just add an insignificant name (changing someone's name might run you afoul of contracts, even in a review copy).
Add a series of random names in the middle of Special Thanks. The names are in a list stored somewhere, so are actually (large base) digits of a serial number.
You want to make it so that the entire binary content of the film looks different for each person, so there can be no point of reference apart from what it looks like (which is the same).
Re: Game of Thrones leak and watermark: a stupid tracking system
#143Re: Game of Thrones leak and watermark: a stupid tracking system
#144Re: Game of Thrones leak and watermark: a stupid tracking system
#145For at least the last 20 years, there are steganographic watermark systems in which inocuous parts of the images are used to hide coded data that stands up to even most lossy recompression. Either HBO is using these and nobody knows yet; or they had an internal leak prior to their application; or they leaked it themselves. Under no plausible circumstances did they visibly watermark a corner and hope for the best.
I looked into stenography for a client who had a problem with audio being leaked by the users of his service. Even though there is a lot less signal in audio, it was trivial to encode a 32-bit pattern throughout the audio track in such a way that it was not discernible to his well-trained ears, and yet it would survive being encoded as a 64kbps MP3. We also checked pushing it through an analog loop, since that was mo…
Re: Game of Thrones leak and watermark: a stupid tracking system
#146> Apart from that I think that binge-watching the first > 4 episodes is a stupid idea that will make you ache > for a month waiting for the 5th episode ☺. For me, I find more enjoyment in binging shows than being drip-fed, I watched all 4 in a row and don't regret not waiting (besides I've waited 12 months I can wait a few more weeks for more.) But more importantly, my online activity means I'll probably be spoiled b…
I honestly think that there needs to be a compromise between the weekly releases common in TV and the season dumps common by streaming services like Netflix. Dumping the whole season at once doesn't allow any communal discussion or suspense, dragging it out over 2 months is meant more to drive revenue for the distributors than the enjoyment of the viewing public. I think releasing 3 episodes a week is probably the op…
This is flexible, and can fit any schedule! You and friends can watch in whatever pattern you want, and it requires exactly nothing of Netflix! You can deploy this method today!
This would unquestionably satisfy your needs. Why would you need anything other than a dump from Netflix?
Re: Game of Thrones leak and watermark: a stupid tracking system
#147About the futility of so called "social DRM", see also http://www.publishersweekly.com/pw/by-topic/columns-and-blog...
Re: Game of Thrones leak and watermark: a stupid tracking system
#148https://www.techdirt.com/articles/20130808/02084524106/time-... "Our experience is that it leads to more paying subs. I think you're right that Game of Thrones is the most pirated show in the world," he said. "That's better than an Emmy." - Time Warner CEO Jeff Bewkes
THAT is a step in the right direction.
Re: Game of Thrones leak and watermark: a stupid tracking system
#149Everyone in her claims that there are mechanisms to add non-visual watermarks into both video & audio, anyone have any suggestions as to what products / systems to use so this can be implemented? Minus writing one yourself (like writing your own framework, you don't know all the gotcha's of an expert)
It's not a very compression-resistant approach and more sophisticated methods are usually used, but a simple one is using the low bits of colour channels. In a red pixel you have bits like so: RED GREEN BLUE 11111111 00000000 00000000 A change in the most significant bit of any of these colours would be massive. 01111111 is half as bright as 11111111. But a change in the least significant bit(s) is barely noticeable.…
Turns out that the least significant bits of a pixel are not uniformly distributed. The obvious example of failure is that you expect more pixels with value 255 than 254, since any overexposure will be stuck at 255. The rest is obvious when you look at a histogram of pixel values; as the number of LSBs used increases you see the curve become stepped.
LSB replacement steganography is easily detectable at about a ratio of about 0.01 bits per pixel. The smarter plan is to add or subtract 1 randomly (or do nothing) in order to match the LSB to what you want; this symmetry is harder to detect (but still very possible, the methods are just more complicated).
The reason you encrypt the data is not just for data security, it is so that the embedder does not have to worry about the data that they are embedding screwing everything up.
tl;dr LSB steganography does not give you any plausible deniability because it's really easy to detect in any type of image at very low embedding levels due to inherent limitations of the process. If you want to use it, you'd be safe with a single message at perhaps a level of 0.005 bits per pixel, but then in a ten megapixel image you'd get 150kB of data which hardly seems worth it when you have to transmit losslessly. Even then, you'd still be screwed at a theoretical level with Ker's square root law.
Re: Game of Thrones leak and watermark: a stupid tracking system
#150Earlier quoted context omitted.
True - and then what? The leaked episodes may have been stolen or can be claimed to have been stolen. Anyway, the horses have bolted and the damage is done.
Yes, but the leaker would be blacklisted from all future HBO (and possibly partner) pre-release materials.