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).
1 Like
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.
2 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 
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 
By the way, you can find all public instances here:
2 Likes
Good luck on your endeavour.
And it’s gone.