📝 Correction | invidio.us #2113

New Issue

2020-11-03T18:16:13Z

foxscore commented

2020-11-03 18:16:13 +00:00

(Migrated from github.com)

Description

invidio.us is no longer running, and only lists alternative instances.
My suggestion would be to either redirect to another instance by default, or tell the user uppon viewing the /providers/video/ page that the original service is no longer online.

Why I am making the suggestion

See description

My connection with the software

None - Was just looking for YT alternatives.

I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.

## Description **invidio.us** is no longer running, and only lists alternative instances. My suggestion would be to either redirect to another instance by default, or tell the user uppon viewing the **/providers/video/** page that the original service is no longer online. ## Why I am making the suggestion _See description_ ## My connection with the software None - Was just looking for YT alternatives. - [ ] I will keep the issue up-to-date if something I have said changes or I remember a connection with the software.

👍 2

oXyiGYJ commented

2020-11-07 01:06:39 +00:00

(Migrated from github.com)

Not sure if directing to an instance would be the best bet, but as far as I understand the code base is still being maintained, could just direct them to that to pick an instance, or add another section of curated/trusted instances?

Mikaela commented

2020-11-08 17:22:49 +00:00

(Migrated from github.com)

If PrivacyTools is linking to specific invidious instances, my solution would be making the actual instance a variable in _config.yml and using it instead of the domain whenever linking to Invidious and in case the instance goes down or there is other cause for replacing it, it would just need one change to get fixed everywhere.

Isn't PrivacyTools hosting a PeerTube instance? Would it be an option to ask for author of linked videos for a permission to reupload them on PrivacyTools PeerTube if they aren't already on PeerTube?

If PeerTube videos are also reachable from other instances (like YouTube/Individious/Nitter/etc. by changing their hostname, I would make PeerTube a variable too.

Example: in _config.yml have invidiousInstance: https://invidious.snopyta.org/ and on pages refer to {{site.invidiousInstance}}/watch?v=dQw4w9WgXcQ"

If PrivacyTools is linking to specific invidious instances, my solution would be making the actual instance a variable in `_config.yml` and using it instead of the domain whenever linking to Invidious and in case the instance goes down or there is other cause for replacing it, it would just need one change to get fixed everywhere. Isn't PrivacyTools hosting a PeerTube instance? Would it be an option to ask for author of linked videos for a permission to reupload them on PrivacyTools PeerTube if they aren't already on PeerTube? If PeerTube videos are also reachable from other instances (like YouTube/Individious/Nitter/etc. by changing their hostname, I would make PeerTube a variable too. Example: in `_config.yml` have `invidiousInstance: https://invidious.snopyta.org/` and on pages refer to `{{site.invidiousInstance}}/watch?v=dQw4w9WgXcQ"`

thansk commented

2020-11-10 20:25:02 +00:00

(Migrated from github.com)

It's good as it is now. Linking to a single instance will over flood it.

👍 1

rusty-snake commented

2021-01-07 13:49:07 +00:00

(Migrated from github.com)

https://invidious.snopyta.org/ shows already a banner:

Please try to use different invidious instances to better the distribute load between them

https://instances.invidio.us/ lists additional information.

https://invidious.snopyta.org/ shows already a banner: > Please try to use different invidious instances to better the distribute load between them https://instances.invidio.us/ lists additional information.

gary-host-laptop commented

2021-01-20 17:44:24 +00:00

(Migrated from github.com)

I can make a PR for this, although it doesn't seem to be a resolution on what should be done.

In my opinion we should redirect to https://instances.invidio.us/ and add a warning about using always the same instance to avoid overtrafficking it.
Also another good option would be to list FreeTube and drop Invidious, since it has been out of beta for some months now, it works a lot better and it is still being updated.

I can make a PR for this, although it doesn't seem to be a resolution on what should be done. In my opinion we should redirect to https://instances.invidio.us/ and add a warning about using always the same instance to avoid overtrafficking it. Also another good option would be to list FreeTube and drop Invidious, since it has been out of beta for some months now, it works a lot better and it is still being updated.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#2113