You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@FireMasterK Ideally invidious should support multiples domain names (or 1 domain name + 1 tor onion). A solution with nginx is "good" but far from ideal.
I actually tried to implement it on my instance. This is a very early commit that didn't work too well but you can take it as a POC and fix it if you want. I don't remember what is broken tho.
It's not easy to implement because the domain is used in several places:
the frontend
pubsubsub functionality
rss feeds
Alternative domains like @Fijxu is proposing is probably the better approach.
unixfox
changed the title
[Enhancement] multiple domains in config file
[Enhancement] multiple domains or alternative domains in config file
Oct 18, 2024
Is your enhancement request related to a problem? Please describe.
Related: #1421
Related comment: #1421 (comment)
Would be nice to have ability to set multiple domains in the config file
"invidious.catspeed.cc" "us.invidious.catspeed.cc" "ca.invidious.catspeed.cc" "mx.invidious.catspeed.cc" "catspeed.i2p" "akjhgaldhfgljkadfg.onion"
Describe the solution you'd like
Would be nice to have ability to set multiple domains in the config file
"invidious.catspeed.cc" "us.invidious.catspeed.cc" "ca.invidious.catspeed.cc" "mx.invidious.catspeed.cc" "catspeed.i2p" "akjhgaldhfgljkadfg.onion"
Describe alternatives you've considered
none
attempt myself
Additional context
I was thinking it would be good feature. I searched for existing issue ticket and none exist only this part of a users comment mentioned briefly.
Originally posted by @Perflyst in #1421 (comment)
also this comment
Originally posted by @TheFrenchGhosty in #1421 (comment)
You could probably then add in your i2p address to the list there as well
Note: this would break video playback (dash) if your domain is not specified in config.
The text was updated successfully, but these errors were encountered: