Or literally use the header files for the widevine blobs freely available in the chromium sources to directly use the API exported by the .so... ... and then g

Or literally use the header files for the widevine blobs freely available in the chromium sources to directly use the API exported by the .so... ... and then get sued for illegally calling a few exported methods on a shared library you freely downloaded from the internet (but without first obtaining a license from Google!). And by the way, I wasn't kidding about the freely downloadable from the internet part, when you open Netflix in Firefox, the browser downloads and loads a shared library from a Google domain: https://dl.google.com/widevine-cdm/${WIDEVINE_VERSION}-linux-${WIDEVINE_ARCH}.zip https://dl.google.com/widevine-cdm/${WIDEVINE_VERSION}-linux... As per https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe37f1 https://gist.github.com/ruario/3c873d43eb20553d5014bd4d29fe3..., which is still used by certain browsers and unofficial clients like the inputstream kodi extension to play netflix videos. If you're on arm, an entire chrome OS image is downloaded instead, extracting the compiled widevine shared library.