Skip to content
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

Closed
3 tasks done
DoraTee opened this issue Aug 13, 2024 · 9 comments
Closed
3 tasks done

Can't watch videos in debug app, login error appears #6347

DoraTee opened this issue Aug 13, 2024 · 9 comments
Labels
bug Something isn't working duplicate This issue or pull request already exists

Comments

@DoraTee
Copy link

DoraTee commented Aug 13, 2024

Steps to reproduce

  1. Enter the debug app
  2. Select any instance
  3. Login to an instance
  4. Try and play video
  5. Error "sign in to confirm you're not a bot" appears
    Screenshot_20240812-195204_LibreTube Debug

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

  • I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
  • I have written a short but informative title.
  • I will fill out all of the requested information in this form.
@DoraTee DoraTee added the bug Something isn't working label Aug 13, 2024
@GlytchMeister
Copy link

I have been getting this in all instances with the regular app as well

@GlytchMeister
Copy link

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.

@BatDevil
Copy link

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.

@akano12
Copy link
Collaborator

akano12 commented Aug 13, 2024

#6116

@akano12 akano12 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 13, 2024
@akano12 akano12 added the duplicate This issue or pull request already exists label Aug 13, 2024
@GlytchMeister
Copy link

GlytchMeister commented Aug 13, 2024

#6116

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.

@GlytchMeister
Copy link

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

@akano12
Copy link
Collaborator

akano12 commented Aug 13, 2024

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.

@QuestioningEspecialy
Copy link

just checked NewPipe v0.27.2 and it works fine 🤷🏿‍♂️

@GlytchMeister
Copy link

GlytchMeister commented Aug 13, 2024

Feel free to fix it yourself then, otherwise you can wait for project maintainers to check during their limited free time.

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. ¯\_(ツ)_/¯

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

5 participants