5 ms·
Sorry to burst the bubble, but this is nonsense. If you don't want something to be downloaded, don't put it on-line.
by shmerl 10y ago
Sorry to burst the bubble, but this is nonsense. If you don't want something to be downloaded, don't put it on-line.
- seanp2k2 10y agoooo, but using the Fetch API requires users to open devtools and right-click something in the network tab, which is surely beyond the grasp of anyone with 5 minutes and Google /s :<
- ominous 10y agoAll true. But one extra step and the most important one: users need to know that is possible. Otherwise they'll never get to point where they know what to google. Most people see websites as they see movies: they type facebook.com and hey, an image. Enter login and password and enter and hey, another image. The fact that things are built on top of other things (websites -> html and assets) is deep magic.
- the8472 10y agoIt only takes 1 user to download it, upload it elsewhere for N users to spread it from there. It's like exploits, it takes an expert to write one, but any scriptkiddy can attack thousands of systems once it has been written.
- Silhouette 10y agoFortunately, if your paid content is also watermarked, you'll know exactly who to sue for copyright infringement in that case.
- AlfeG 10y agoIts impossible in mobile chrome
- dchest 10y ago5th comment in the bug report explains why this is an issue even when the website is not trying to prevent downloads: https://bugs.chromium.org/p/chromium/issues/detail?id=675596#c5 https://bugs.chromium.org/p/chromium/issues/detail?id=675596...
- austincheney 10y agoPerhaps they are new to web development. This is the nature of developing for the web: you have to perform cross-browser testing and you have no control over media. The only thing you can do is test upcoming browser versions and respond appropriately. They do release future versions as canaries. Developing for the web has always been this way. If the dev doesn't have time to be a commercial web developer then they should hire an assistant.
- uxp 10y ago> If the dev doesn't have time to be a commercial web developer then they should hire an assistant. Some companies that do web development (commercially, internally, or whatever) have tighter release schedules than the cool DevOps style Continuous Deployment that we see the unicorn startups like Basecamp, GitHub, Slack, etc. doing where code can get pushed to production a dozen times a day. The place I work at has governmental regulations and SLAs we have to comply with when we deploy, which puts us on a cadence with something akin to Chrome's release schedule (e.g., Dev is CI/CD, QA is CD, UAT is kept to about once a week, Prod is every 4 weeks with capabilities at a 2 week hot fix window). Additionally, we just don't have the resources or budget available to keep one developer twiddling his or her thumbs all day waiting for new buttons to show up on a browser control that we have to hide or mitigate the impact of. I completely understand what your argument is, and it's valid. We have QA run integration, regression, validation and smoke tests any time code is promoted up the environment chain that tries to catch issues like this, and we do our best to keep on top of it all. This issue isn't something that effects us, but it shows a reactionary approach to dealing with these issues. Teams that do spend their time reacting to changes like a new button, or an underlying OS update breaking some compatibility or what-have-you have always been a thorn in my side. It's no way to deliver value to their customers since their time is consistently being hijacked from new features to put out fires, which is stressful and leads to burn out very quickly.
- izacus 10y ago> Sorry to burst the bubble, but this is nonsense. If you don't want something to be downloaded, don't put it on-line. Or lobby really hard to implement DRM into browsers and lock down all devices allowed to access internet right? :P
- fdsafEWSF4yt654 10y agoThrowaway account The mean reason why DRM will be used in HTML5 will not be for media but for advertising. Blocking ads will then be targeted as circumvention of DRM. Google et all must be drooling at prospect of unblockable ads
- logicallee 10y agoYou're making this as a throwaway, but obviously are not writing anything controversial here. So are you leaking industry information to us? Why not write more. It might be slightly off-topic but no more than the rest of this thread and it's interesting.
- i336_ 10y agoContinuing in the vein of the other reply comment here, do you have any suggestions for workarounds, loopholes or things that would be a good idea for us to do to fight this, if things are as suggested?
- bastawhiz 10y agoHow exactly does the DRM work when I refuse to download the DRM-protected content? That's like saying I'm circumventing DRM by not renting movies to watch in my Bluray player. Your comment is nonsensical.
- cookiecaper 10y agoThat's an easy one. Construct the page so that the client can't tell the difference between real content and ads. There's no inherent reason ads have to be served from ad-specific domains or downloaded into HTML elements that are detectable as ad space. That requires you to download the whole package, including ads. Then, when the client attempts to analyze the content before display, it could potentially be construed as "circumventing DRM". Pre-legal speculation disclaimer: IANAL. They'd have to define DRM as not only preventing ripping the video outside of its normal context but any type of alteration prior to display, even if it occurs after the encryption module terminates. That'd be hard because the decoder ordinarily makes some alterations to the decrypted video stream, e.g., scaling for different displays, overlaying subtitles, applying filters, etc. HDCP is intended to make DRM circumvention apply to any intermediary devices, like capture cards, but that wouldn't work for computers since HDCP is just working between the display and the GPU driver, if it supports HDCP; the program used to playback the content would be unconcerned with this. Again I'm not a lawyer but I don't see how blocking ads could be construed as counteracting DRM, as long as the analysis is occurring after the normal decryption cycle. The wiggle room for publishers is probably in whether or not destroying the ads creates a "derivative work" or not. The consumer's argument that the page is not saved and displayed only temporarily would probably not work due to the RAM copy doctrine. Things like the Family Movie Act [0], which was passed in 2005 to pre-empt a lawsuit filed against ClearPlay, a DVD player that provided fast-forward and mute macros to bypass objectionable content in legitimate DVD copies, would not apply since they explicitly authorize "making imperceptible [...] limited portions of the audio or video content of a motion picture [...] for private home viewing"; scope limited to motion pictures only. Ad blockers have been challenged several times in European courts, where they've won, but I don't see how they could expect to win a copyright challenge in American courts (beyond blatant judicial activism). My assumption is that big shots like Google have not pursued this yet because they're more worried about the Streisand Effect than allowing relatively advanced users to install ad block. Knowing that the blockers are legal in Europe, there's probably nothing they could do to stop people from using them, and it'd just create a huge PR issue. Maybe the DRM angle is intended to get European courts to rule against ad blockers? I don't know. [0] https://www.copyright.gov/legislation/pl109-9.html https://www.copyright.gov/legislation/pl109-9.html
- nsgi 10y agoAs some of the comments mention, the download button is an issue for sites that are using third party content which they have permission to use, but not to allow users to redistribute. Unlike browser extensions or even right-clicking on the video, a download button implies that users have permission to download the video, and arguably even to share it, which could get the site owners into trouble unless they develop custom controls to remove the download button.