I suppose you can simply inspect the element and remove this attribute.
var video = document.querySelector('video'); video.controlsList.remove('noremote');
Just change 'noremote' to 'nodownload'
That's an overly broad and vague statement to excuse entitlement. I'm fine with downloading content that's publicly available, but not because "they had it coming."
And why did publishers start playing those games? Because too many visitors were abusing the trust they had before.
Regardless of how they feel it's all workaroundable (inspect)
Not in this case. There are plenty of alternative ways to serve video content that aren't easily copied through any standard browser tools. Every single one of them is more user-hostile and more at risk of breaking something useful than using plain ol' HTML5 video elements where most people aren't going to abuse them even if technically they could.
I find the request window especially hard to use on sites with a lot of assets (e.g. SoundCloud loading a million avatars for a song) as the performance slows to a crawl.
The vast majority of publishers don't use those tricks.
The worst offender now is the applying of click event handlers for links that simply navigate to a URL. The inability to open a link in a new tab only because the developer chose to use a <span>/<div>/<li> that triggers a javascript framework routing action, instead of using an <a> tag pointing at that route... sigh.
I know publishers hate this, but publishers don't exactly have a good track record of treating their user well. Non-copyable text, hijacking right click. Regardless of how they feel it's all workaroundable (inspect) but still a hostile user experience.