Announcing invidious.io, and the deprecation of invidio.us

[TheFrenchGhosty]

TL;DR at the bottom

---

Due to multiple issue with invidio.us:

• Domain still owned by Omarroth

• .us domains requiring US citizenship

• The content was hosted on a personal server used by omarroth for other things (this is now changed)

---

Changes to invidio.us:

invidio.us is now deprecated, and later will only redirect to invidious.io.

The content still on invidio.us is now hosted on a VPS, dedicated to Invidious, which @Perflyst and me ( @TheFrenchGhosty ) control.

---

News:

A new domain was obtained: invidious.io and the content is now hosted on an Hetzner VPS in Germany.

Both the domain, the VPS, and everything else related to Invidious is now managed by @Perflyst and me ( @TheFrenchGhosty ), the project is now bus factor resistant.

The invidio.us domain is still owned by Omarroth (this won't ever change).

We would like to deeply thanks everyone who donated cryptocurrencies, allowing us to buy the new domain, and pay for the VPS for some months. A detail of the January expenses will soon be available in https://github.com/iv-org/transparency

---

TL;DR:

invidio.us is now deprecated, invidious.io is the new domain.

The invidious-redirect website ( invidio.us ) is now https://redirect.invidious.io/

The instance API ( instances.invidio.us ) is now https://api.invidious.io/

The uptimerobot page ( uptime.invidio.us ) is now https://uptime.invidious.io/

https://git.invidious.io/ redirects to the Github page of the project: https://github.com/iv-org/invidious/

https://docs.invidious.io/ redirects to the documentation website of the project: https://github.com/iv-org/documentation/

https://invidious.io/ will become in the future a "project presentation" page (like https://searx.me/ ), we will use a markdown framework like Hugo.

Projects using something from invidio.us need to move to the new domain.

---

FreeTube by @PrestonN, and NewPipe by @TeamNewPipe already moved, other developers are strongly encouraged to move as soon as possible.

Some developers that have projects that currently depend on invidio.us:

• @SimonBrazell (with Privacy Redirect)

• @zedeus (with Nitter)

• @cloudrac3r (with Bibliogram)

• tom79 (with UntrackMe) - Edit: The developers were contacted on Mastodon UntrackMe isn't affected because the instances list is self-contained: https://framagit.org/tom79/fedilab_app/-/blob/master/content/untrackme_instances/payload_2.json

I strongly enourage everyone to ping developers of projects that you know use or depend on something hosted on Invidio.us.

[SimonBrazell]

So no "official instance" like invidio.us used to be?

[TheFrenchGhosty]

@SimonBrazell invidio.us was shut down months ago, and was just a redirect page.

See #1321

This is just a move to a new domain name.

I mention you in case Privacy Redirect uses instances.invidio.us

[SimonBrazell]

Yes I realise that but wasn't that just because you guys couldn't access the domain / server? I was just thinking the project would benefit from having an officially maintained instance again like prior to the author's departure.

[SimonBrazell]

And thanks for the heads up, much appreciated, but I don't think this change will impact Privacy Redirect.

[TheFrenchGhosty]

@SimonBrazell

I was just thinking the project would benefit from having an officially maintained instance again like prior to the author's departure.

I would like this to be a thing, but we don't have the funding for this. I did the math a while ago, and concluded that to have a public instance (with dash enabled by default) we basically need to spend more than 300€ monthly.

This isn't possible for now, and won't be for a really long time.

[SimonBrazell]

we basically need to spend more than 300€ monthly. This isn't possible for now, and won't be for a really long time.

Fair enough, those costs sound very high to me but I guess the servers I build don't typically deal with the kind of load invidious would.

Thanks again for letting me know about this and clearing this up, all the best!

[TheFrenchGhosty]

@Mennaruuk Thanks a lot for contacting all those projects developers!

[Mennaruuk]

ABSOLUTELY! My pleasure :)

[probonopd]

Will there be something like https://instances.invidious.io/ anytime soon?
A page where one can link to, which contains the different instances (without mentioning "shut down", "coming soon", etc.)?

[TheFrenchGhosty]

@probonopd Yes this is planed. For now you can use https://docs.invidious.io/Invidious-Instances.md

Later we will have something on instances.invidious.io

[Hahlh]

Hey everyone!
I really appreciate, that you are caring about privacy and constructive discussions like this help us move forward and figure stuff out as a community.

Having said this, would it be alright for you to have this moved to the discussions instead?
I have subscribed to this so that I would be updated about the further developments regarding invidious.io and I believe, that a separate issue or discussion would be preferrable to keep this issue on topic.

If you and the maintainer prefer to keep this here, no worries.

A wonderful day to everybody!

[TheFrenchGhosty]

I definitely agree with @Hahlh

Cloudflare is fundamentally bad, and the way we handle it won't change (we might actually write more reasons why it should be avoided).

Please move this Cloudflare discussion to another issue.

[unixfox]

...I was really hoping for support/to be compatible with older network protocols too this time around (in the new one), like TLS 1.0, 1.1 & 1.2, SSL's and/or whichever of this type/kind, so I can actually open/load this from/with some of my 'bricks' and pick a instance that will work/load for me...

BTW - I can use only some of the instances/mirrors on those devices (with older browsers - on purpose or not, for couple of reasons), the ones that don't enforce TLS 1.3 and the .Onion(s) by taking advantage of Tor2Web (.ly), but most of them don't function properly (they use old source vers. or whatever) and since cookies aren't remembered/stored via this method - I can't make any changes/set settings preferences, or even switch to the dark theme...

Also it would be nice if the default rez. (JS-off, Android's native ExoPlayer - rez. user preferences/settings are not being used in this case at all) can be brought/reverted back to 720p, like before (long time ago, over a year), instead of 360p as it's currently - on code basis, so all the instances can use it and don't change it.

Feel free to run your Invidious instance if you want to use it on older devices. We are not going to support TLS 1.0 & TLS 1.1 anymore because those TLS protocols are bad for the security.

Btw I think you are going off topic.

[drogga]

...I was really hoping for support/to be compatible with older network protocols too this time around (in the new one), like TLS 1.0, 1.1 & 1.2, SSL's and/or whichever of this type/kind, so I can actually open/load this (.io redirect site) from/with some of my 'bricks' and pick a instance that will work/load for me...
Please don't just don't tell or try to convince me that v1.3 is enforced basically on everything nowadays for a security reasons, privacy (which is simply a joke in 'modern' days) or whatever else bullshit - there's no point.

BTW - I can use only some of the instances/mirrors on those devices (with older browsers - on purpose or not, for couple of reasons), the ones that don't enforce TLS 1.3 and the .Onion(s) by taking advantage of Tor2Web (.ly), but most of them don't function properly (they use old source vers. or whatever) and since cookies aren't remembered/stored via this method - I can't make any changes/set settings preferences, or even switch to the dark theme...

Also it would be nice if the default rez. (JS-off, Android's native ExoPlayer - rez. user preferences/settings are not being used in this case at all) can be brought/reverted back to 720p, like before (long time ago, over a year), instead of 360p as it's currently - on code basis, so all the instances can use it and don't change it.
The DRM (like music videos) content (HLS/Dash - separate A/V streams) can still be made to keep playing in 360p (MP4's with mux-ed/build-in audio) in those cases.

Also: Other than YT (App or Site) nothing can open age restricted channels like "Bud Light", for which you need to login to YT and be over 18\21 to even see the channel's content (uploads\videos), even none of the invidious instances can't open\load those channels, like the one i mentioned, let along NewPipe, SkyTube ot whatever else, tho their content is playable as a separate individual videos...

[TheFrenchGhosty]

@drogga This is offtopic, and @unixfox answered you. We're not going to support outdated protocols.

[drogga]

Ok.
Also there is more than that, my comment contains multiple suggestions (let's say), ignore it if you want, I did/had wrote what I wanted to say.
No, it's definitely not a off-topic !, if you reRead some of the other (not hidden) comments, then you will see off-topic ones.

I don't feel the need to digg or discuss it any further, so Bye from me.
You are free and it's your choice to believe in what you want.

...No one forces anyone to reply, so if 'somebody' wants a 'clean' topic, then this individual needs to stop commenting or even lock the thread if possible...

(@)unixfox - Noted (understand-ed), thanks for the suggestion anyways, but I prefer to not open any new issues/tickets !
Take care, all the best ;)

I'll probably delete my comments after some time anyway.

(@)TheFrenchGhosty - OK, I agree with you, a small part on this (now in 'italic' is indeed a bit of 'off'.
BTW - if you read carefully, you will see that I actually didn't "ask" for anything, those are just observations and 2 suggestions with carefully picked words.

[unixfox]

@drogga

If you want to suggest some modifications into the code of Invidious then please open a separate issue. We welcome all new feature request.
This issue is about the website invidious.io not about restricted channels nor the default resolution of a video.

Let's keep this issue clean and exempt of off-topic. Multiple people are subscribed to this issue and receive a notification for every new comment. The least that they want it's to only have comments related to the initial subject into their notification inbox.

Thank you for your understanding.

[TheFrenchGhosty]

@drogga

No, it's definitely not a off-topic !, if you reRead some of the other (not hidden) comments, then you will see off-topic ones.

So asking about instance-stuff in an annoucement of the new domain of the project isn't offtopic now?

Just open your own issues.

[Noisefox]

It would be cool if we could donate on a Patreon opencollective liberapay or Ko-fi

[TheFrenchGhosty]

@HkopMD We already explained before that it's not really possible for us to do that.

Also, snce, currently donations are owned by the project and not by someone, it's even less do-able.

However if you really want to donate you can donate to people who work on invidious directly, most of them have way to receive donations, but yes, those donations won't go toward the project.

[Noisefox]

@HkopMD We already explained before that it's not really possible for us to do that.

Also, snce, currently donations are owned by the project and not by someone, it's even less do-able.

However if you really want to donate you can donate to people who work on invidious directly, most of them have way to receive donations, but yes, those donations won't go toward the project.

:( I wanted to donate so you guys have the money to make an official invidious instance. But ok, and thanks for the quick replay

[unixfox]

@HkopMD We already explained before that it's not really possible for us to do that.
Also, snce, currently donations are owned by the project and not by someone, it's even less do-able.
However if you really want to donate you can donate to people who work on invidious directly, most of them have way to receive donations, but yes, those donations won't go toward the project.

:( I wanted to donate so you guys have the money to make an official invidious instance

Unfortunately for the time being running an official invidious instance would be too expensive. The maintainers of Invidious already talked about it on Matrix, and they decided against deploying it one.

Maybe they will reconsider this possibility when Invidious will be rewritten (in another programming language).

As a maintainer of yewtu.be I would surely offer my help if one day they want to deploy a production ready official Invidious instance.

[github-actions]

This issue has been automatically locked since there has not been any activity in it in the last 30 days. If this is still applicable to the current version of Invidious feel free to open a new issue.