[1] https://github.com/castlabs/electron-releases/issues/33#issu...
As far as I know, if you download a Firefox binary from firefox.org, you can use Widevine, and there's no source in that binary that's not open source, but the binary is signed in such a way that you can download the component. If you build Firefox on your own, Widevine won't work. Can you do the same thing with Metastream? Allow users of the Metastream binary from you to get Widevine, but not allow people who build it on their own to get the production EME codec? (I realize this is more frustrating for Metastream dev than Firefox dev because Metastream is primarily about playing videos, but it should still work.)
Or in other words, is Widevine permitting Firefox to do something they're not permitting you to do, or are you trying to be more open than Firefox?
(... That said, apparently Widevine works fine in e.g. Debian's build of Firefox? So what's different?)