Backends are more than just scrapping the watching page, gotta also scrap the search page. (possibly even the main page although not sure)

Also, Invidio.us doesn't allow you to disconnect entirely, the video still comes from Youtube/Google.

But sure, we can use it for obfuscation of search results but it's ehh

Invidious exposes an API that I imagine would be much easier to use than scraping the page.

@lionirdeadman is correct that videos still come from Google, although I expect them to be proxied with iv-org/invidious#34.

Neato. I wish you good luck though. Proxying Youtube videos for everyone sounds incredibly tough.

I'd like to see support for syncing subs with an invidious instance (public and custom)

I often share video to social network and IM. It will be great to share with invidous url instead of youtube.

This can be at least optional with setting

Maybe you could get it so you can log into your Invidious account to sync everything.

Just like to add my voice to the mumble!
This feat would be great, then I wouldn't have to figure out a way to let newpipe pass my google-filter in afwall:)
I wish I'd have the skill to contribute!

How is the status?

Also Invidious provide a "&local=true" parameter which load the video completely from their own server, without any Google connections to Enduser

Any updates on this?

Still waiting for this…

@Stypox Would this not fix TeamNewPipe/NewPipe#3612? Also this would be awesome, maybe add it to v.0.20.0? I really want this now, after I turned off Tor for NewPipe, this would really be great for that new proxified solution :D

Also Invidious provide a "&local=true" parameter which load the video completely from their own server, without any Google connections to Enduser

As it was already mentioned before in this thread, we won't scrape invidious but use their API.
I don't know how to have invidious videos from their API, it's returning videos from googlevideos.com and i've tried local=true parameter, but it didn't work. One result seems to be proxied with invidious instance: dashUrl, but it may fall under TeamNewPipe/NewPipe#2415 bug.

Alright @B0pol. Maybe skip the proxified parameters. But as TeamNewPipe/NewPipe#3710 mentioned and I did in #3612(Comment) wouldn't it solve reCAPTCHAs?

I'd say yes, I haven't seen anything about rate limitation or captcha in api documentation. But I'm not sure.

Unless YouTube puts Captchas on ytimg.com (for thumbnails) and googlevideo.com (videos), but I doubt.

Alright @B0pol. Maybe skip the proxified parameters. But as TeamNewPipe/NewPipe#3710 mentioned and I did in TeamNewPipe/NewPipe#3612(Comment) wouldn't it solve reCAPTCHAs

I think this is one of the biggest reasons Invidious must be supported. YouTube just bothers too much with the CAPTCHAs when using VPN, in my case.

It would be nice to see a list of instances to select, like PeerTube, so that users can add their own instances

FYI, Straw-viewer (Invidious version of YouTube Viewer) uses the Invidious API and it hasn't give me any issues yet (like Google trying to block me)

Any updates on this?

+1 on this. The invidious api is much more stable, will not break constantly like youtube does. Plus will not use google's servers directly for anyone who cares about this. Another plus is that they don't make you fill out a captcha time to time.

I would like to see this utilised as well. Considering this is my go to for YouTube on Android I would like to hit my own local invidious self hosted instance

Quoting @SamantazFox from #789:

If anyone plan to work on that, it'd be preferrable to wait that we start working on an API v2 (or at least a remaster of the v1). Many things needs to be done on our side to ensure consistency across the API and make it more usable.

Also, it'd be awesome if we could have more instances hosting just the API, as the current official list is quite overloaded by bots scraping our API.