The extension already has Remote CDM functionality, and this only performs CDM functions on the remote server, and requests to the license server are still made from client-side. Therefore, even if you use Remote CDM, cookies and other sensitive information will not be sent to an external server so you can use thirdparty Remote CDM securely. However, in UnsafeRemote mode, all information obtained by the extension is sent to an external server, and all processing, including requests to the license server, is handled within the external server. Therefore, in UnsafeRemote mode, a malicious server operator may be able to obtain sensitive information and perform session hijacking. Do you really want send Amazon cookies to stranger?
The extension only supports static CDM file names due to Javascript limitations and cannot use names such as "(wildcard).wvd". If enough people are frequently switching between multiple CDMs, I would create a tool to facilitate CDM switching.
Currently, licensing schemes are created for specific license servers and are managed by splitting certain files into multiple files to avoid bloating one file. And I considering creating a heuristic scheme to automatically challenge and dynamically detect one of the licenses. This allows supporting for multiple license servers without bloat a file extreamly. Do you think this should be added? Also, do you think it should keep old specific schemes that covered by heuristic scheme after it is added?