I’ve done this for about 6 months, I’ve had a very mixed experience with Invidious, mostly with YouTube constantly making changes without notice or the video stream not really supporting resuming if the connection breaks briefly.
This isn’t a comment on the Herculean effort the contributors are taking on, but new users should be aware that they need a very reliable connection, update the container regularly, and exercise patience in the current state of Invidious.
Yeah, anything to make that line go up on YouTube’s end.
The latest tag still doesn’t support multiple audio tracks, which might sound niche, but YouTube just rolled out AI dubbed audio tracks, and so Invidious can just play the wrong track and you can’t do anything about it and it’s been this way for about a month.
That being said, it seems that the team’s plan is to put more dev time into changing the back end to video.js so they don’t have to brunt the video retrieval workload, and video.js supports multiple audio tracks as far as I know. I look forward to when that happens, but in the meantime the latest tag is not 100% usable :(
I’ve done this for about 6 months, I’ve had a very mixed experience with Invidious, mostly with YouTube constantly making changes without notice or the video stream not really supporting resuming if the connection breaks briefly.
This isn’t a comment on the Herculean effort the contributors are taking on, but new users should be aware that they need a very reliable connection, update the container regularly, and exercise patience in the current state of Invidious.
YouTube has litterally attacked it by blacklisting all know cloud IPs world wide when tmaccessing YouTube.
Self-hosting is the only reliable way. Sometimes, YouTube breaks something, but after a few hours, Invidious pushes a fix…
But if you target the latest tag of all relevant images, itms just:
docker compose pull; docker compose down; docker compose up
Yeah, anything to make that line go up on YouTube’s end.
The latest tag still doesn’t support multiple audio tracks, which might sound niche, but YouTube just rolled out AI dubbed audio tracks, and so Invidious can just play the wrong track and you can’t do anything about it and it’s been this way for about a month.
That being said, it seems that the team’s plan is to put more dev time into changing the back end to video.js so they don’t have to brunt the video retrieval workload, and video.js supports multiple audio tracks as far as I know. I look forward to when that happens, but in the meantime the latest tag is not 100% usable :(