Skip to content

Feature Request | Move the Special Rules list #409

Description

@spirillen

What is the feature you'd like to request?

I suggest we moves the rules.py contests of:

self.regex_active2inactive = {
r"\.000webhostapp\.com": [
(self.switch_to_down_if_status_code, {410, 424}),
],
r"\.24\.eu$": [(self.switch_to_down_if_status_code, 503)],
r"\.altervista\.org$": [(self.switch_to_down_if_status_code, 403)],
r"\.angelfire\.com$": [(self.switch_to_down_if_status_code, 404)],
r"\.blogspot\.": [self.handle_blogspot],
r"\.canalblog\.com$": [(self.switch_to_down_if_status_code, 404)],
r"\.dr\.ag$": [(self.switch_to_down_if_status_code, 503)],
r"\.fc2\.com$": [self.handle_fc2_dot_com],
r"\.github\.io$": [(self.switch_to_down_if_status_code, 404)],
r"\.glitchz\.me$": [(self.switch_to_down_if_status_code, 403)],
r"\.godaddysites\.com$": [(self.switch_to_down_if_status_code, 404)],
r"\.hpg.com.br$": [(self.switch_to_down_if_status_code, 404)],
r"\.imgur\.com$": [self.handle_imgur_dot_com],
r"\.liveadvert\.com$": [(self.switch_to_down_if_status_code, 404)],
r"\.myhuaweicloudz\.com$": [(self.switch_to_down_if_status_code, 403)],
r"\.skyrock\.com$": [(self.switch_to_down_if_status_code, 404)],
r"\.sz.id$": [(self.switch_to_down_if_status_code, 302)],
r"\.translate\.goog$": [(self.switch_to_down_if_status_code, 403)],
r"\.tumblr\.com$": [(self.switch_to_down_if_status_code, 404)],
r"\.vercel\.app$": [(self.switch_to_down_if_status_code, 451)],
r"\.web\.app$": [(self.switch_to_down_if_status_code, 404)],
r"\.wix\.com$": [(self.switch_to_down_if_status_code, 404)],
r"^s3\.ap-south-1\.amazonaws\.com$": [
(self.switch_to_down_if_status_code, 403)
],
r"^u\.pcloud\.com$": [(self.switch_to_down_if_status_code, 302)],
r"\.wordpress\.com$": [
(self.switch_to_down_if_status_code, 410),
self.handle_wordpress_dot_com,
],
r"\.weebly\.com$": [(self.switch_to_down_if_status_code, {"404", "406"})],
r"\.zzz\.com\.ua$": [(self.switch_to_down_if_status_code, {"402"})],
}

As this is plain json, I suggest this part is giving it's own branch or REPO to avoid waiting to long for updates, You should grant a number of users moderator rights on this files AND the requirements of two moderators approval before it's merge able.

This can remove the stalled time and properly a lot of merge issues such as #404

What problem are you trying to solve?

I'm trying to solve a problem where...

What solution would you like to see?

A single point of "failure" awaiting a single users approval, for something that should be rather flexible for a number of trusted users to merge and maintain, and this list should not be depending on the rest of the pyfunceble project + is can be shared to other project.

Are there any alternatives you've considered?

I've considered alternatives such as...

Additional context

This JSON file should be a JSON5 file, to allow adding comments inside the file, for easier maintenance.

Activity

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

Metadata

Metadata

Assignees

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions