2 ms·
You could try and break this by adding something like some random noise or jitter maybe, or slightly transforming the proportions of the pages perhaps, or shift
by asdff 5y ago
You could try and break this by adding something like some random noise or jitter maybe, or slightly transforming the proportions of the pages perhaps, or shifting colors in a stochastic way would probably complicate their efforts. The frame around the photo will no longer be exactly 1.1231 mm and will throw off their embedded code reading systems. The colors won't be the same hex codes they are expecting and won't be shifted evenly. Spacing is now all off between the characters.
- viraptor 5y agoGood information hiding and watermarking doesn't get affected by common transformations. Most changes will be relative to other content, so noise and resizing shouldn't impact it, especially if there's redundancy in the fingerprint codes. It's not "frame is 1.1231 mm == 1", but rather "frame is slightly wider than average of other pages == push 1 into FEC".
- asdff 5y agoHow would be able to get past stochastic transformations? "frame is slightly wider than average of other pages == push 1 into FEC" could be stymied by making pages randomly wider or narrower, so now the average is different and the frame you are expecting to be slightly wider may even be slightly narrower than the average now, garbling your encoding.
- viraptor 5y agoSure, but you're taking two things for granted: you know this is the approach used, and it's the only approach used. If we assume those, you can work around any watermark.