Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request]: Multiple instances (allow fallback to a second custom invidious server) #5791

Closed
3 tasks done
mooleshacat opened this issue Oct 4, 2024 · 1 comment
Closed
3 tasks done
Labels

Comments

@mooleshacat
Copy link

mooleshacat commented Oct 4, 2024

Guidelines

  • I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
  • I have searched the documentation for information that matches the description of the feature request I want to file, without success.
  • This issue contains only one feature request.

Problem Description

I have an issue where my primary Invidious instance fails, but then FreeTube ("FT") will fall back to one of the hard-coded instances.

I would like to put in a second instance instead of using a random public instance

Proposed Solution

Allow multiple instances - maybe using a multiline textbox

I would prefer it if I could put a list of instances, in order of priority, into a text box so that I can have it fall back to my other private instance instead of a public instance. You could also list a public instance at the end, as a last resort, if the other instances in the list did not work.

Alternatives Considered

There are no alternatives other than forking FT project and adding code in yourself

Issue Labels

improvement to existing feature, new feature, new optional setting

Additional Information

An example of this list could be:

http://192.168.1.100:3000
http://192.168.1.101:3000
https://invidious.privacyredirect.com:443

The above list is in order of priority.

@mooleshacat
Copy link
Author

This is actually a duplicate of #3048

Apologies, I did search but I did not notice that ticket and read it.

@efb4f5ff-1298-471a-8973-3d47447115dc efb4f5ff-1298-471a-8973-3d47447115dc added the U: duplicate This issue or pull request already exists label Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

No branches or pull requests

2 participants