Notices by Invidious (invidious@social.tchncs.de)

Follow up announcement:

Server updated! (I also updated the server used for the Matrix-IRC bridge).

Everything went perfectly.

(I didn't realize the server was still on Debian Bullseye so that was really needed :3)

Announcement:

I'm updating the main Invidious server (running Invidious.io, the documentation and various other stuff), things might be down or half broken for a bit.

-TheFrenchGhosty

@migtorr Hello! An extension like libredirect is the best solution that I know of. By using the "auto pick instance" button, it automatically gets an instance from our updated list (here: https://docs.invidious.io/instances/) and if you end up on a broken one, the extension menu has a shortcut to remove it from your list.

- Samantaz Fox

@JackRacc The 6h cut-off is caused by Youtube providing playback links that expire after that amount of time.

We could add some logic for the client to tell the server to fetch a new link, though it's not garanteed that the video player (VideoJS) won't pause the video to reload the new data.

Also, this is very low priority, as reloading the page "fixes" the problem in all cases.

-SamantazFox

@JackRacc You can use Yattee if you have access to an instance that doesn't block API

https://github.com/yattee/yattee

(Using the testflight version is best)

@JackRacc Okay, so the problem is unrelated to the captcha. Because HD720 was removed by Youtube, we changed the default quality to "DASH", which is not supported by the current version of our player (VideoJS 7) on iOS.

We're planning to update VideoJS to the next major version (8), but until then, all you can do is select the "medium" quality in the preferences.

-SamantazFox

@JackRacc I have forwarded that to more knowledgeable people. I hope this can be easily solved!

-SamantazFox

@JackRacc Hello! So what you say is that Safari for iOS can't run the captcha? Or am I missing something?

-SamantazFox

@rberlim Hmm, that's weird, because we publish containers for both amd64 (x64) and arm64 (aarch64) platforms.

For historical reasons, the main image needs to be changed to `-arm64` for that to works, but all other images (sig helper and companion) the same tag can be used for both:

https://quay.io/repository/invidious/inv-sig-helper?tab=tags&tag=latest

https://quay.io/repository/invidious/invidious-companion?tab=tags&tag=latest

-SamantazFox

Is #Invidious finally dead and buried for good? So, #RIP and let's move all our #video content to #Peertube? Other ideas?

#Fediverse #culturalHeritage #freeCulture

@debacle

No it's not.

Public instances are struggling but private instances work perfectly.

-TheFrenchGhosty

We have also added a new page to the documentation that lists the most common error messages returned by youtube, and some guidelines to help you out:

https://docs.invidious.io/youtube-errors-explained/

-SamantazFox

Hello everybody!

We've released a new stable version of Invidious, which fixes the very annoying "Youtube API returned error 400" error on the channel pages.

It however does not change the video playback capabilities of Invidious: currently a PO token/visitor data pair and inv_sig_helper are required to watch videos. We're still working on a solution that make them optional.

A lot of other bugs were also fixed. Read the full changelog here:

https://github.com/iv-org/invidious/releases/tag/v2.20241110.0

-SamantazFox

@spirillen

You sir are an idiot.

None of us, the invidious team and the public instance owners owes you anything.

You're not happy about it? Go pay the server hosting bills to those instance owners so that they can enable proxy (spoiler: 100-200€/month minimum) or go away, or you know, be productive and go host multiple public instances with proxy enabled. yourself. It's FOSS, you're not happy about it, you can do the work yourself.

-TheFrenchGhosty

@amici choose dash as quality in the settings (some instances might have that disabled)

-TheFrenchGhosty

Hello,

TL;DR: *.invidious.io down temporarily

During our move to a new uptime checker, a change was made to the invidious.io DNS...

This worked... except our provider's ( @njalla #njalla ) name servers fucked up and haven't pushed anything (other than a deletion of the existing entries).... meaning all our DNS just disappeared from the internet (except for the rare DNS that cache)...

I already opened a support ticket with them...

Don't worry though... we're still alive!

-TheFrenchGhosty

@njalla We're back!

-TheFrenchGhosty

Haven't heard of PeerTube yet?


It's a great piece of software to host your own videos!

Plus, they don't break 3rd-party clients, especially on a Saturday. Unlike some other plaftorm(s).


Go check out them out at @peertube


Or start searching for content with https://sepiasearch.org/

Hello!

A new version of invidious is available!

Huge thanks to LuanRT from the youtube.js project. He's the one who found a fix!

Please wait a few minutes for the container releases to be available through Quay (especially the arm64 one).

-SamantazFox.

Hello everyone!

We are aware that Youtube has changed something, and that something broke all instances.

We're working on a fix, please be patient!

Also, please don't open any Github issues for that. It isn't helpful, and the bot will close them anyway.

-SamantazFox