Closed doronbehar closed 5 years ago
There is a way to support all of them dynamically but:
UPD: I will still add this feature.
this way requires parsing a file which is not supposed to be machine-readable and has no stable format (this is the whole point of this extension but I'd like to avoid it when I can)
You are not talking about reading that WiKi page where all the instances are listed right?
If you are thinking about implementing this via a text box in the preferences that will have just a list of all hostnames that should be considered as invidious websites, doesn't sound too complicated to me, unless you wish to parse it in a very safe manner, i.e make sure spaces and other disallowed characters in every line..
I've added functionality that you've requested in the branch custom-match-patterns. Is this solution fine?
Update: it's in master now, so you could test it from there.
Looks awesome @f1u77y :smiley: I've tested it from master and the design is excellent. I have 2 questions / remarks on the UX of it:
invidio.us
) by default but this match pattern is not seen as included..*://invidious.snopyta.org/*
and it worked. EDIT It will be nice to add this link somewhere in the settings page.
Since the invidious connector was merged, I've learned that there are several public invidious instances. A list is available here: https://github.com/omarroth/invidious/wiki/Invidious-Instances Users (myself included) could have wished to make the connector work for them in their preferred instance.
I was wondering, do you think web-media-controller could dynamically or via a user preference set a hostname for which the connector will work with? If not, perhaps we can at least update the list of hostnames for this connector from time to time according to the list?