3 ms·
And, it doesn’t even help much, as the actual image is still accessible to the browser, unless executed on the server.
by kuschku 12y ago
And, it doesn’t even help much, as the actual image is still accessible to the browser, unless executed on the server.
- verelo 12y agoYeah that was my other concern, but like all forms of DRM, it's pretty much broken from the start so initially I didn't think it was worth pointing out. I'm glad you did though. It's an important and likely not obvious point to some people that as the image is being modified in JS, the original image is locally accessible regardless of the watermark if the viewer is even just a little tech savvy. Might be good for getting credit on printed pages, but its certainly not a complete solution.
- kpil 12y agoIsn't it kind of obvious that if you want to modify something in the browser, the browser must be able to load it? There is no standard for "trusted" downloads yet, in the sense that everyone except the user is "trusted" nowadays... I'm sure it will come though.
- kuschku 12y agoThere is one, with HTML5 DRM, but again, this is only code running in userspace on your computer, so any CompSci student can just disassemble it and get the image again.
- verelo 12y agoTo you and me for sure, but a photographer who is not familiar with how JS is executed, I would say its possible they might miss the issue and just focus on the result.