LibreTube is fixed 🎇

I have switched to FreeTube and actual YouTube via VPN than logging in and fighting with YT’s BS moves.

Again, the communication of the developer absolutely sucks, even GOS handles their communication with users better than Libretube does. Whether it’s one person or not, a new user will go looking for help from the community and give up because its not being handled correctly.

Incorrect. I have Proton VPN on, the free tier. And, if I turn it off is the same result.

1 Like

I’m not sure about including this kind of suggestion because it indicates that readers must meet certain conditions in order to use the app.


With that said, I’m tentatively marking this thread as waiting since much of the functionality of LibreTube (for a majority of people[1]) depends on the health of Piped and its public instances, as outlined here by a maintainer of both LibreTube and Piped:

my playlists, which have been backed up separately, could only be restored empty

Bnyro: They can’t be restored while Piped fails to extract video information, thus that’s expected and will work again in case Piped is fixed one day.

I’ll be monitoring the LibreTube and Piped issue trackers regularly and post any new developments here. Of course, anyone else is very welcome to do so as well.


  1. Unless you’re able and willing to self-host your own private Piped instance ↩︎

1 Like

I guess you have hidden the icon that should appear in the notification bar when using a VPN.

Can you tell me which server you’re connected to?

Proton
US#372060

Tried to make a video to share but it seems that we are only allowed to upload images here .

So let me get this straight. LibreTube is not working when you disable the proxy option either with a VPN or without a VPN. But if you use public instances, it’s also broken.

So there’s no way to make LibreTube work.
And the IP blacklisting thing is BS.

And, while most Piped Instances are broken as well, official mirrors such as piped.video are working fine. So Piped in itself isn’t broken.*

LibreTube could fix the issue, by using piped.video as a temporary solution, but they haven’t, and seemingly wouldn’t.

I don’t hate Liverpool too. I tell you it was a good replacement for the non-dead YouTube bank. But if it doesn’t work for whatever reason, I think it should be removed. I mean, I haven’t seen someone here said that it actually works. So if it’s now working, whether it’s because of pipes or anything else, it should be removed.

*Since TeamPipe advise against using instances, one could say you should only measure Piped status with mirrors.

2 Likes

I didn’t use a VPN just over my actual ISP.

18 Aug 2024, by discourse@privacyguides.org:

This is the only app that actually works. NewPipe and Tubular haven’t worked for quite a while if your IP is blacklisted.

Grayjay doesn’t work either unless you login and enable authentication in plugin settings.

LibreTube is the only app that worked and still works, but is a little bit of a hit-or-miss depending on what kind of nonsense YouTube is doing.

If we remove LibreTube, then we might as well get rid of NewPipe too.

Just in keep in mind most people have a different experience.

That being said, what Piped instances are you using ?

The results are quite close. I believe we should add a warning, as this is a good middle ground. I will make a PR later today.

Will be something like :

LibreTube is broken for most users. Only use it if your IP is blacklisted by Youtube. If so, you will need to find a Piped instance that is not blocked by YouTube.

Indeed. I also experience problems not too often. So, it’s not completely broken. Sometimes, I need to switch invidious.
I use Yattee on mobile, and main piped instance in pwa on desktop.

1 Like

Again, I don’t think that this warning is a good idea, at least with its current wording.

What I will say does not define my position in this thread, but if LibreTube is “broken for most users,” then why is it (still) recommended on the site?

Again, I’m not calling for the removal of LibreTube; I’m suggesting that it’s strange to open the warning with this statement without any elaboration.

1 Like

Any warnings or removals wouldn’t make sense.

We need to wait and see how LibreTube and NewPipe deals with these issues.

I will also quote an Invidious team member:

Everyone in the Invidious team does not have unlimited free time, we work at our own pace. It’s much more complicated to solve than any previous YouTube breakage. Hence, why it takes a lot of time to get a fix.

We know we are probably losing many users, but it’s part of the life of an open source project. Usually an open source project is run by volunteers and users should not expect the same reliability as a product run by a company where many developers are working on the product every day.

What’s said above also applies to LibreTube, NewPipe, and Piped.

3 Likes

As @Lukas say, it can still be useful if you want to bypass an IP ban. The warning should be clearer about that.

This one managed to play this video for me in Libretube after trying 30 different instances and most other videos remain broken.

For me Tubular still manages to play if not everything most things like a breeze.

With Libretube is always this painful game of hunting the instance that eventually will pass the video that you need to watch. User experience wise for me has been terrible over the last months.

Nevertheless, I don’t think it should be removed from the recommendations. The only message that should be added is that if one of the recommendations doesn’t work try the other one. I think we all can accept that what works for one may not be the solution for other.

1 Like

Generally speaking, I noticed that videos in the Home/Trending section usually play, but not the rest.

From my experience, LibreTube has always been broken way more often than NewPipe. I prefer to use LibreTube because the UI is nicer, but I often can’t.

I think that LibreTube is pretty great, but the developers just can’t keep up with Google’s bullshit…

Update from Bnyro (LibreTube maintainer):

3 Likes

No why is works fine

So they just published a new version, that apparently fixes the issue. (Haven’t tested myself).

This is great, and I am glad that it got fixed. I just hope that in the future, the dev will acknowledge the problem and say “look, this is gonna take a long time to fix”, rather than refusing to acknowledge it and then suddenly dropping a release.