Related: https://news.ycombinator.com/item?id=25849800

The major players of the industry have DRM keys, and browser competition is hindered by only allowing access to DRM protected contents to some other vetted major players.

Nasty situation. But I guess it makes sense from the POV of the entities that want to protect their contents with DRM (if DRM was opensource... its use wouldn't make much sense)

This seems relatively unlikely, mainly because the drm issues are likely related to widevine, which google is notoriously picky about who they allow to use it

This is nothing qutebrowser can fix - DRM/Widevine support is something done entirely by the underlying QtWebEngine and Chromium code.

It's a bit of a pain to set up, but it should be possible to get it to work. Basically, you'll need to get an older Chrome version (corresponding to whatever Qt version you're running), extract the needed .so files from there, and then put them in the right place so QtWebEngine picks them up. Unfortunately, there's almost no feedback when it doesn't work.

Here's a rough guide: https://www.reddit.com/r/qutebrowser/comments/jwb90w/how_do_...

Alternatively, someone there reported installing Google Chrome on the same system did help.

Qutebrowser runs on top of Blink, which is the same guts that are in Chrome. So if Widevine is packaged for some other browser that is available on your distro, you can pass in the QT arg

"widevine-path=/path/to/google/chrome/WidevineCdm/_platform_specific/linux_x64/libwidevinecdm.so"

and it should work. This even works on NixOS, although you have to pull the relevant path out of the Nix store, and I don't know a good way to do that automatically that can fit inside a qutebrowser config.