-
-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't watch videos in debug app, login error appears #6347
Comments
I have been getting this in all instances with the regular app as well |
I tried using piped directly and got the same error, and their issues page has this same topic. Current speculation is that piped instances are getting blacklisted whack-a-mole style by google. Quickly, too, because its effecting even brand new ones. Some Invidious instances are using a tool to cycle through IPv6 addresses, but sometimes entire IPv6 ranges are getting blocked. Sounds like youtube/google is cracking down hard on FOSS frontends. |
instead of y'know, fixing their hellscape platform that promotes scams, even the CIA said you should use an AdBlocker, that's how bad YouTube is. |
That one is closed, and the last comment says "tldr just change instance", which... Doesn't solve the problem. All instances are down because of this. New instances are down. And according to TeamPiped/Piped#3658 (comment) , patching getAuthtoken is unrelated, and YouTube API keys don't work, because they'd need to be used in the Piped back end, not just the frontend. And that's the only speculated solution I've seen that isn't just "lol use a different instance" They're all blocked. I just went and tried all of the instances listed in the app. |
Disabling the piped proxy whilst using VPN doesn't solve it either, for what its worth, but I get the distinct impression I'm talking to a wall |
Feel free to fix it yourself then, otherwise you can wait for project maintainers to check during their limited free time. |
just checked NewPipe v0.27.2 and it works fine 🤷🏿♂️ |
There's a difference between acknowledging there is an issue and saying "we'll get to it when we can" as opposed to saying "do this thing that you literally just said doesn't work" and closing the issue. I fully understand contributors and maintainers have limited time to spend on foss projects. But telling users to get bent or do it themselves and then putting your fingers in your ears and going "lalalalalala" doesn't exactly inspire confidence and trust. I've since switched to newpipe. I don't need to worry about using Libretube's proxy since I have a kill-switched VPN, but up until now, I wanted to support Libretube in what little ways I could because I liked that this project went the extra mile to use a proxy, which made me think the project was more serious about privacy and protecting users from Google's hostile and unethical practices. I guess I know better, now. |
Steps to reproduce
Expected behavior
When you enter the debug app and login and play a video, the video should play.
Actual behavior
I enter the debug app and it doesn't allow me to play a video no matter what instance I choose.
LibreTube version
Debug v 0.24.0
Android version
Android 12
Other details
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: