Fix Visitor Data Producing Invalid Tokens Due to URL Decoding #21
Conversation
|
How comes this is an issue? The visitordata used in the official www.youtube.com web interface, also ends with |
|
If you use the one ending in %3D, Invidious does not work. |
|
Reviewing the PR, that's very odd. Could you do a video recording of installing invidious normally with docker: https://docs.invidious.io/installation/#docker then make the comparison with This will help me a lot to understand what's going on. Thank you |
|
Does your installation of invidious allow 1080p / 4K video playback with tokens that have %3D suffixed? |
How this has to do with 1080p video playback? |
|
Invidious does not allow you to play 1080p / 4k (anything above 360p) unless you have the "DASH (adaptive quality)" setting as it defaults to medium and requires those two tokens to enable the higher quality playback. |
|
But you need these two tokens for medium too. This is why I don't get it. You are trying to say that DASH does not work without the |
|
Yes, my main goal is to be able to watch videos at normal quality (1080p), initially, I was only able to watch them at 360p and then discovered that DASH allows it but only if you have the two tokens. When generating the tokens with this tool, it did not work initially until i removed the |
|
Ok! Great. Thank you for the feedback, now I understand much better the issue. |
|
Hello, On www.youtube.com, the visitordata also ends with |
|
Perfect, I am on TrueNas and using invidious through docker and it did not work for me. Should it persist, I'll open an issue 👍 Merci pour lê voir. |
During the process of grabbing the authentication tokens from YouTube's API, there is an issue where the
Visitor Datatoken is returned with URL encoded padding characters (%3D) which is the ASCII representation of the equals character (=).The fix is decoding the URL through python's standard library;
urllib, we use it's.parse.unquote()function and then strip the characters from the end usingrstrip('=').