[Feature Request] Support Spotify WebPlayer about ttth HOT 11 CLOSED

@philipphutterer
sorry for the long break - i was not able to work on this project now for several weeks.
I will try to start working on it, but to be honest i don't see a chance to work on this particular issue.

Will most likely focus on updating the inner core with the next versions and not by adding more services in the near future.

Therefor i am closing this for now - sorry again for the long wait without outcome.

from ttth.

Thank you very much for your first issue to this project. It is much appreciated.

from ttth.

Hi @philipphutterer

first of all - thanks for the issue ;)

i'll take a look on that later. I don't have a spotify account myself - so testing might be a problem for me. i'll update this post in the next days to let you know if i think i can add support for it or not.

Greetings

from ttth.

@philipphutterer

Unfortunately, using the Custom URL option did not work.

could you tell me what does not work?

from ttth.

In the normal browser version you are able to log in to listen to music. In ttth you are only redirected to download the app or sth like that.

from ttth.

Hi,

i can listen to some promoted things there ... but i really don't know what spotify is supposed to be like and what magic spotify is doing in the background.

ttth is more or less a browser - opening url's in tabs - with some service specific inject code to provide goodies.

If opening the spotify url in ttth results in another content then opening it in your default browser - using the same browser-agent ...then it feels like some strange voodoo on the spotify side.

wondering

from ttth.

Okay after searching around some more i think i figured it out. Spotify uses DRM to play their contents and the browser therefore must have a plugin what Firefox, Chrome and Safari all have. Because Chromium isnt Chrome it does not have this plugin (called Widevine). And since Electron is based on Chromium its missing this plugin s.t. the starting page might that in order to serve the correct content.

Edit: Actually i tried it and it works on Chromium. Sorry for the incorrect statement above.

This Brave issue thread was quite helpful.

from ttth.

I also tried to navigate directly to the spotify web player within an electron instance and it did not work either. Then i changed the user-agent properly s.t. "electron" was no longer in there and it worked properly. Another thing i recognized is, that you use electrons <webview> tag that implicitly uses an iframe. i am not sure but maybe this could also be a problem somehow?

from ttth.

Okay after searching around some more i think i figured it out. Spotify uses DRM to play their contents and the browser therefore must have a plugin what Firefox, Chrome and Safari all have. Because Chromium isnt Chrome it does not have this plugin (called Widevine). And since Electron is based on Chromium its missing this plugin s.t. the starting page might that in order to serve the correct content.

Edit: Actually i tried it and it works on Chromium. Sorry for the incorrect statement above.

This Brave issue thread was quite helpful.

thanks that info is valuable.

from ttth.

I also tried to navigate directly to the spotify web player within an electron instance and it did not work either. Then i changed the user-agent properly s.t. "electron" was no longer in there and it worked properly. Another thing i recognized is, that you use electrons <webview> tag that implicitly uses an iframe. i am not sure but maybe this could also be a problem somehow?

i'll play around with it if i can find some time

from ttth.

This issue seems to be stale

from ttth.