youtube_rss VS Piped

Of course, it's a bit tedious to do that a lot, so I eventually coded my own application that circles through different circuits with each request. That way, if one operation is blocked, it you just retry and it usually works. The advantage is you don't need to redo all the web interface navigation, since navigation as such is done in a local application instead.

I'm a bit of a YouTube-junkie, but I don't like Google because they're super invasive when it comes to privacy. So to be able to comfortably and anonymously follow my favourite channels without a Google account, I made my own YouTube client, youtube_rss.

Use an open source YouTube client that doesn't show adds instead. I coded my own, that suits my personal needs perfectly, but for most people, who want a graphical interface, I would recommend using something else, e.g. FreeTube.

I found now that Piped includes duration in the RSS so might script around that. Wonder if Invidious could add that metadata too.

https://github.com/TeamPiped/Piped/wiki/Instances

Yattee

https://github.com/yattee/yattee

it requires either public or private Piped or Invidious instaces [1].

1. https://github.com/TeamPiped/Piped/wiki/Instances

2. https://docs.invidious.io/instances/

For Safari (macOS or iOS/iPadOS) you could look into extensions like Vinegar or StopTheMadness, although you’ll likely need to work out if they’ll conflict with your other extensions. Failing that, an Invidious or Piped instance is likely your best bet.

Sometimes a half-solution will do, like Invidious or Piped.

[0] https://invidious.io/

[1] https://github.com/TeamPiped/Piped

Try deleting all cache and cookies and update all filters from ublock origin, otherwise we need to wait for an update. You can use Piped in the meantime.

piped.video