-
-
Notifications
You must be signed in to change notification settings - Fork 446
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
FAQ - "Sign in to confirm you're not a bot" #6389
Comments
Works as expected when not using a VPN.
Just letting you know this in order for this error to be made non-fatal, the stream block itself was kind of expected. |
That's unfortunate, I haven't tested this with a blocked IP before the release :/ |
0.25.1 should have fixed that. |
I'm sure I speak for most users here, so I just wanna take the moment to share some ❤️: You do an amazing job, so with all my heart: Thank You! ❤️
I've got one question, one note for other users, and a suggestion about that:
|
Regarding 1): I suspect that the feeds will definitely work better again after more people use Piped again, since one of the ways the feed is being updated is by users that visit the channel manually. In theory there should be other methods as well, such as Pubsub, but I'd need to go deeper into Piped's code for that again. It's likely something else is broken there somebody needs to look into. |
(i don't feel like making a seperate issue) Something loke this has actually happened to me. I posted about it on my Mastodon account: the installers for both LibreTube and LibreTube Debug 0.25.1 just don't work, flat out. No matter what version I use, I get hit with "App not installed." and I don't know why. I'm using an Android 10 OneUI Samsung Galaxy A20. |
i'll try restarting my phone. |
ok so the lt* installer still doesn't work
|
ok quick update: the newest nightly build worked; i don't know if i was doing something wrong beforehand |
Hi! I'm a bit confused by the current "solution": if piped proxies are disabled and everything is running straight through Youtube, what's even left of this app? Why use it if I have to disable it's primary privacy-related functions and rely on less private solutions (VPN, as recommended)? Why is this posed and a "solution" if it doesn't solve anything? And why refuse invidious if you don't have capacity to solve it? |
I never cared about the piped proxy, just use a VPN if you care about not directly talking to YouTube. I care about:
The past few days I still used Libretube to find videos and shared the link to Newpipe to play them (I hate the Newpipe UI). |
Which was the definitive feature of this app when compared to alternatives? Sure, you do you. It seems like you've completely missed the point of my comment: the main issue is that the "FAQ" explains how to "fix" the problem with "Sign in..." as if it is a solution when it is clearly not. Explain better, blame Google clearly, tell that it is an unfortunate situation (with unclear future) - none of that is currently in that post and it is misleading. |
A VPN isn't less private. Youtube would'nt get your device information, so everyone using LibreTube will look the same. Now, of course this is the theory and google could still fingerprint you in some other ways.
Look, I'm not a big fan of LibreTube. But you know that Invidious doesn't proxies the video at all ? When you go to yewtu.be, your devices is directly contacting Google's servers. So your solution to use Invidious isn't one, since Invidious never proxied videos. All other successful Android YouTube clients (NewPipe and Grayjay) never proxied videos. You still get the advantage of no ads and no trackers (except IP-based). Plus SponsorBlock, downloads, etc... |
@I-I-IT doesn't https://docs.invidious.io/instances/ have instances? and instances work as a proxy? |
It is depending on the VPN provider. It's not just about connecting to Google, it's also about routing connection through a 3rd-party. Should you trust your VPN? Probably not. Same might be true about instances, but I assume they are curated at least in some way - and connecting to them is reserved to Youtube only, while VPN on Android is "global" per se.
Quick search led me to this: https://github.com/iv-org/documentation/blob/master/docs/geoblocking.md - so looks like they do proxy connection? Plus, it wouldn't make any sense to find a solution with session tricks only to connect a client to Youtube again. |
long awaited |
Not quite. Go into your network console, and you will see a connection made to "Google Video". They might proxy it once they obtained a video playback link (such as https://rr2---sn-5hneknee.googlevideo.com/videoplayback?expire=1724607865&.......), but you still make the initial connection to Google servers. That being said, there is an option to proxy videos. BTW, for those wondering, the patch does work well, even with a VPN. |
If you don't trust your VPN, have you considered using the tor network? Worked for me. |
Doesn't work for me, I get "Network Error" toast message! |
I found the solution. You need to register on Settings / Istance/Account anything to register a username and a password possibly long and complex ( but remember it) Then on proxy enable “Disable Piped proxy” then enable "Local stream extraction" ... That is all now all the videos go to me , I hope it is the same for you too |
How I can use this code? |
I can't find local streams extraction in settings. Help me please. (I use latest fdroid version). Why you don't have search in settings? |
I'm sorry, but I don't think this is a solution. I'm just pointing this out because I've been logged into my Piped account for months, both through the app and through the browser, and all the errors are there in full force... I think we can all agree that LibreTube isn't as much to blame as YouTube; not only did they come up with a new ads injection system directly inside the videos, but it was implemented in a way that blocks third-party apps. And I really mean that apps get messed up with one error after another. I don't know if there will be some developer/modder or whatever that can bypass that as well. I hope so, guys. LibreTube was really a beautifully made app. |
Thank god i can finally use libretube again. |
Hello, can anyone tell if this "Got Error: sign in to confirm that you're not a bot" is a LibreTube bug and will it be fixed within upcomming version or do I have to use some "special" method or setting? (The one cited by I-I-IT does not work with my LibreTube). I use local VPN. NewPipe works fine. Thank you. |
Why do I need this app if I need to enable VPN, I wanted to use it without it, because the traffic is not direct, but if it doesn't work I can also enable regular YouTube and watch the same((((. |
Getting this error sometimes when I tap the download button. I have followed all of the steps to make libretube work, and it is still sporadic at best, but trying to download is even less reliable, and results in a crash. Download Crash Log
|
I wonder if there's a way to sign in with dummy accounts like Aurora does with the play store. |
It still does not work with these settings. The same error keeps showing. |
This comment was marked as off-topic.
This comment was marked as off-topic.
Even with the great recommendations, it's still not working (using VPN). |
I'll even login with a Google account just to have the better interface and features than Revanced. I'm not sure if providing that as an option would even fix the problem or not but if it does I'd likely just settle for that. |
I am currently having the issue on the debug version. Update: the stable seems to have no issue. Both have local stream extraction and proxy bypass enabled. |
Idk if piped will copy invidious on how they fixed it. |
First of all, please make sure you're on the latest version (0.25.1).
FAQ about the current situation
Settings
->Instance
and enableDisable Piped proxy
as well asLocal streams extraction
. Disclaimer: The bot-blocked API call will now be done directly from your IP address, which is obviously less privacy-friendly. Using a VPN is recommended, but might not always work since YouTube blocks IPs of VPN providers as well.The text was updated successfully, but these errors were encountered: