Open DataM0del opened 1 month ago
The original reason to go the Widevine route is because that is how the Spotify website works. For Grayjay plugins we attempt to mimic browser clients as closely as possible to maximize compatibility. That doesn't mean we won't consider something else at some point but I wanted to explain a little bit of the thought process behind choosing to use Widevine.
The original reason to go the Widevine route is because that is how the Spotify website works. For Grayjay plugins we attempt to mimic browser clients as closely as possible to maximize compatibility. That doesn't mean we won't consider something else at some point but I wanted to explain a little bit of the thought process behind choosing to use Widevine.
I think the Spotify desktop app uses playplay? So why mimic the website when you can just mimic the desktop app, you have a OSS library to decrypt it, so there's no strings attached, whereas with Widevine, it will try its hardest to hide a video from OBS.
You can just use the playplay API, which does return the encrypted music, but then you can use unplayplay (I still don't understand why some people use political places to host their software, maybe just because anywhere else where Spotify or some big corporation is looking will allow them to file a DMCA takedown because it decrypts their DRM, but as long as they're not in the US because that's the only place that allows you to take down stuff due to DRM circumvention, but you could just use Codeberg or your own self-hosted instance instead and as long as you & the server are in the EU, there's probably no reason to comply with them) to decrypt the music. Way better than using Widevine in my opinion because Widevine is way more intrusive than playplay because playplay is just clear key DRM & you even can see the source code because they transformed it into C code, plus Spotify isn't controlling it as it's just the procedure to decrypt, nothing else.