- cross-posted to:
- hackernews@lemmy.smeargle.fans
- opensource@lemmy.ml
- cross-posted to:
- hackernews@lemmy.smeargle.fans
- opensource@lemmy.ml
Anyone who’s been using privacy-respecting frontends for some time will recognise Piped. A YouTube frontend with no ads, integrated SponsorBlock, return dislikes, and a customisable UI.
Piped also allows you to subscribe to as many channels as you want without ever logging into a Google account. You can export your subs list from YouTube and import them to Piped seamlessly.
If you’ve never heard of it, give it a glance at https://piped.video. For more instances, check here.
Is this a similar concept to NewPipe?
Yep, Piped uses the NewPipeExtractor to load videos, just like NewPipe. However, Piped runs it server side, and NewPipe runs it client side. YouTube likes to rate limit the big instances too, so all you have to do is use a smaller one like il.ax or piped.adminforge.de.
Doesn’t this make NewPipe better in that instance? If it’s client side you aren’t going to be rate limited.
There is also a fork of NewPipe that integrates SponsorBlock (I don’t know if Piped has that).
What’s the advantage of running this server side?
That youtube don’t know YOU scrape their website. in fact, they don’t even know you’re watching a video.
However, YouTube rate limits big Piped instances, so it’s better to use NewPipe or a small instance.
Small instances it is ^^
A couple days ago I found a service called Farside, apparently you can replace youtube.com with farside.link/piped to redirect to a random smaller Piped instance. It works pretty well for me, although sometimes I just use il.ax because I’m just lazy and don’t want to type that much.