spotify-tui VS widevine-l3-guesser

It was at this point I was getting a lot of joy out of writing command line applications. I had also just learnt of the existence of spotify-tui and wanted to explore more I could build such applications. So building interfaces for APIs felt like a good way to try this out.

If you are handy with a terminal, spotify-tui is my favorite Spotify controller I’ve ever used. No bullshit at all.

I switched to linux recently and iam loving it the speed and CLI tools that linux provides are amazing you can do anything imaginable in the terminal i use Spotify in the terminal navigate very very fast using auto-jump and its just easier than navigating all those uis and using the keyboard for everything is way faster and easier on your hand than the mouse and keyboard combination especially if you use a window manager

I dont know if it counts but I have used spotify tui on my pi400 a while ago link

November 2019

For example, there's a couple reddit clients, YouTube viewers, Spotify clients and many many more.

If you want to run Spotify on a Raspberry (or PinePhone or some other device), there’s Spot, which is great, but kinda heavy and slow. There’s Spotify-qt which is faster, requires messing with Spotify developer dashboard, and UI doesn’t fit on small screens. Spotify-qt is itself based on Spotify-tui which runs in the terminal (pretty cool IMO). And a bare client/daemon is spotifyd. So you have quite a few choices there.

Web-DL and Web-rip are different things done differently. Web-DL requires using scripts that utilize cdm keys to download the webstream. I have no idea if this script works anymore, but this script can (or could) extract l3 cdm keys to use for downloading https://github.com/Satsuoni/widevine-l3-guesser. Webrip involves using hdmi splitters to record the stream.

If they have DRM you need to find the keys using a Widevine Guesser, then download the encrypted file and decrypt it using either ffmpeg or mp4decrypt.

the widevinedumper script is a bit tricky, would be easier if you download the code for widevine-l3-guesser, open the content_key_decryption.js file, on line 106 you should see this, edit it with your own key, then add the extension to chrome

If the course doesn't use DRM then https://github.com/r0oth3x49/udemy-dl otherwise https://github.com/Puyodead1/udemy-downloader and https://github.com/Satsuoni/widevine-l3-guesser with downgraded CDM to 2209 (might stop working on Udemy in the future though, but it still works for now)

only downside is that you have to provide the decryption keys, the main way was using this extension https://github.com/Satsuoni/widevine-l3-guesser but google updated their DRM recently which broke it, not sure if it still works on udemy if you downgrade to the old CDM version or not.

> Is that even possible for Spotify at this point?

Spotify are using Widevine on their web client, which is considerably more annoying to deal with than the encryption method used in the files fetched by Psst.

Nothing is stopping them from only serving files from the endpoint that serves Widevine protected files.

Then again, Widevine L3 has been broken[0], Google just keeps rotating the private keys used in the content decryption module.

[0]: https://github.com/Satsuoni/widevine-l3-guesser