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]: Better storage for Invidious instances #1910
Comments
It cannot arbitrarily add instances because the extension would need to ask permission again when that happens |
Could there be a feature to run through the list of instances and check if the plugin has permission. If not then prompt permission from the user. Like a button in the settings |
I don't think a changelog list would make sense at all, wouldn't [...default list, ...custom list] make more sense as you can add your own changes independently of bundled instances and they can be deduped at runtime/ when permissions are added |
I'm not 100% sure this will work (but it seems to in Firefox with my test extension), but what if you:
Still would take some work to implement, and I'm sure there are better solutions. |
In theory yes, but in practice no. |
Currently Sponsorblock stores the list of Invidious instances via two methods.
The issue here is that you can either get an updating list where you can't make changes or an old list with your changes that does not update. Both have problems and are not an ideal solution.
Usually a lot of invidious instances get discontinued or are buggy and you need to add new ones even when SponsorBlock has not updated. This is horrible UX and makes using Sponsorblock very cumbersome with Invidious.
I propose an alternate way to do this.
In the new proposed way only the list of changes should be stored instead of all of the URLs. Example:
Then when Sponsor block is loaded the list of changes is applied over the list from the source code.
This would fix the horrible UX of dealing with Invidious instances as well as be more storage efficient than storing all of the URLs.
The text was updated successfully, but these errors were encountered: