Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Ability to remotely disable broken features #3529

Description

@fregante

Crazy idea, but occasionally we have very breaking bugs that cause frustration: #3527 #2357 #1805 #1148 #2700 etc

These are often fixed quickly, but users have to suffer it until the browser updates the extension, which could be a day later.

We could have a mechanism that pings this repo to check whether a feature should be temporarily disabled. For example inside globalReady

const options = await optionsStorage.getAll();
const hotfix = await cache.get('hotfix');
fetchHotfixesAsynchronously(); // `cache.function` to be run up to ~4 times a day?
Object.assign(options, hotfix);

fetchHotfixesAsynchronously could fetch the content of a dedicated, locked issue with a content like:

false

or

{"cleanup-repo-filelist-actions": false, "unaffected": "20.9.4"}

fetchHotfixesAsynchronously would use looseVersionCompare to compare unaffected with the current version and either store {'cleanup-repo-filelist-actions': false} or {} accordingly.

Notes

Performance: up to 4 fetches a day should make it lightweight enough
Privacy: it would only fetch public content on GitHub, only if you open GitHub
Security: it would only GET JSON content from api.github.com, it doesn't POST anything

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedmetaRelated to Refined GitHub itselfsmallIssues that new contributors can pick upunder discussion

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions