I'm pretty sure there are options, none of which are efficient, but here they are:
1. Firefox consumes the Widevine as a plugin, and the way to load that may be a straightforward one, through an interface.
2. Support a different DRM scheme that has an open interface and is popular
3. Disassemble Widevine or talk to hackers who've understood it. Clean room disassembly is legal in many parts of the world.
4. Don't drop this project, but put up a placeholder and evangelise better DRM standards. Pretty sure that if it involves crypto and it's not open source, it is an attractive target with an exploit in the works. That's what it is going to lead to, and by then you'd already have a working implementation.
1. Firefox consumes the Widevine as a plugin, and the way to load that may be a straightforward one, through an interface.
2. Support a different DRM scheme that has an open interface and is popular
3. Disassemble Widevine or talk to hackers who've understood it. Clean room disassembly is legal in many parts of the world.
4. Don't drop this project, but put up a placeholder and evangelise better DRM standards. Pretty sure that if it involves crypto and it's not open source, it is an attractive target with an exploit in the works. That's what it is going to lead to, and by then you'd already have a working implementation.