-
Notifications
You must be signed in to change notification settings - Fork 103
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
Suggestions on shadowrocket blacklist #55
Comments
Thank you for your suggestions. The first point may be completed in the next few months (also, pull request welcome 😁), I have been too busy lately, and I have almost no time to maintain the current project. There are two problems with the second point:
|
I think if accessing google is not through IP address, it should be processed by these lines:
If you want to add more IP addresses to the blacklist, it should cause performance issue. I asked the author of shadowrocket more than a year ago that its rule matching algorithm uses a trie tree, so I try to keep the shadowrocket rule list around 5000 lines. In this case, it is generally recommended to use whitelist rules. |
Thanks. Regarding the second point, at this moment I am not aware of any missed Google domains in gfwlist. However, new domains for new Google services can often be added, but the gfwlist may not be updated in time. On the other hand, the chunks of common Google IPs are almost unchanged (so it may not be a concern for a less frequent update) and short (the impact on performance should be very minor). Edit: it seems there is an official list here. |
I think this should be the upstream project needs to handle 😂.
Good point, It may be added after a long time, I am too busy. lists: |
First of all, thanks a lot for the project, which helps a LOT!! I just two minor suggestions on the rule of generating the shadowrocket blacklist, just for your consideration.
dl.google.com
andicloud.cdn-apple.com
will be proxied.The text was updated successfully, but these errors were encountered: