-
Notifications
You must be signed in to change notification settings - Fork 22
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
Prevent future outages #16
Comments
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Well, I'm pretty sure that everyone who is using this extension have recently experienced outages. Those outages are caused when (e.g. Github) change html structure of website without further warning.
I need manually find out how much was html structure changed and then fix it. This can vary from several minutes to several hours (YES, hours, because in GH, you need to use
observer
to observe DOM changes and listen onpjax
events). Most of time, it takes maximum day-two to fix a problem.But nowdays, we have much bigger problem - publishing an extension to chrome store (which has most users). Since chrome changed privacy & polices of store extensions, reviewing updated extension can take several days to weeks - depends on extension size and size of userbase). During that time, user has still broken extension :(
in short:
So, my idea to prevent further outages is to be able to temporally turn off extension on specific websites without user knowing it or letting him/her to turn off extension on specific websites. This could be also useful for Gitlab users, which can have different Gitlab versions (old self-deployed version).
What do you think ?
WIP (popup branch)
The text was updated successfully, but these errors were encountered: