I deployed a new public Invidious instance

New public invidious instance: https://inv.thepixora.com

Unlike the other public instances, this one is API available so it can be integrated into 3rd party clients like Clipious, Yattee, etc.

It is now listed in the official Invidious instances API: https://api.invidious.io/

Privacy note: It is proxied behind cloudflare.

I plan to continue maintaining this instance up for the forseeable future, and would love to see how it performs under heavy user load.

14 Likes

My concern like with any front end is how long it will last or let YT let it last. I know you said you’ll be continuing to maintain it and I’m so thankful for anyone who does that but I still kinda question the longevity of such a project.

1 Like

It will not last because of upstream YouTube changes, not because of the instance maintainer or the Invidious team commit activity.

I know. That is what I meant. And it makes the maintainers job a lot harder and at some point, many give up. Hence my questoning of the lengevity.

1 Like

Yes, I eventually reached that point during the end of last year, so now I no longer maintain any privacy front-end instances.

I’m glad to have more instances, but you make a valid point about the longevity and usability of them. At this point I’m just saving everything I watch with yt-dlp and deleting them when no longer needed because YouTube’s upstream changes break front ends way too often to be reliably usable (not the maintainer’s fault).

2 Likes

this rocks! Made FreeTube usable again, which is perfect timing since Grayjay basically requires me to login to a Google account to watch a video these days.

3 Likes

This no longer works on Freetube for me, although the instance itself still works ok.

1 Like

Do you use the official code or the one from Nadeko? Asking because the latter seem to do a lot of work to make things better.

BTW, thanks for the instance and the help you just provided (a working backup to Nadeko)

2 Likes

@anon25722375 I don’t (yet) contribute to the Invidious code repository, so the code being usable or not doesn’t really depend on me. However as @FranklyFlawless pointed out, YouTube does change its functionality a lot which does break things here and there. In case you mean copyright reports and the like, they shouldn’t be an issue on my instance, it is not difficult to harden websites against them.

Giving up on maintenance means you don’t use it. I personally use this all the time so I don’t see myself “giving up” anytime soon :sweat_smile:

1 Like

@Encounter5729 I’m using the official code, otherwise I would have to add a link to the modified source according to Invidious public instance rules.

This very instance is evidence that deploying a public Invidious instance without an antibot/PoW, modifying the source, or blocking the API and 3rd party clients, is entirely doable :upside_down_face:

By the way, you can find all public instances here:

2 Likes

Good luck on your endeavour.

And it’s gone.

1 Like

@Expert4870 How so? Maybe a connection error or some downtime. It isnot gone at all… :thinking:

2 Likes

Maybe @Expert4870 refers to the fact that the thread was unlisted.

2 Likes

At this point I’m trying to replace as many YT subscriptions in my RSS reader with PeerTube ones since those can be played by my media player just fine. Unfortunately in situations where the only alternative platform for a YouTuber is Patreon, there’s no RSS feed for that.

1 Like

It was redirecting to either the nerdvpn or nadeko instance when you searched for a bit. Perhaps it broke and now they fixed it.

1 Like