Closed Benyamin-Tehrani closed 10 months ago
The geosite is awesome and works well.
You should not edit geosite file but append your own DOMAIN-SUFFIX rules in the config file. Or you can regenerate the geosite file, for more, you can see the origin geosite repo.
About to use gfwlist instead, yeah, it's ok for your traffic saving purpose, however in china many foreign site was not fully banned by gfw but still has weak connectivity (the best example is github), we need these site to use proxy.
Maybe you can try to contribute the docs, and I think that the usage of geosite in default example is accetable.
Examples are just examples, you can use whatever method you want, I don't use geosite at all
I can download the file from browser. but CMFA throws error above.
I don't quite understand why you created this issue. Based on your description, you've already looked into Loyalsoldier's GitHub repository, where the geosite file actually includes the gfwlist. It's labeled as geosite:gfw
.
If you switch to the release branch, you can see the daily updated txt files (which meets your readability requirements).
My proposed solution to this problem is: To convert the existing geosite data source into clash text-format rules with github actions, and then release rule-providers, which can solve the current lack of well-maintained clash rules and avoid the drawbacks of geosite.
Loyalsoldier also creates a repo for rules of clash https://github.com/Loyalsoldier/clash-rules These rules are generated from Loyalsoldier/v2ray-rules-dat and v2fly/domain-list-community according to README. They will do the trick for you.
My pal, I almost got the right opposite idea of yours 😂. I do enjoy geox‘s tidyness and inclusiveness. It's better to offer an option, which makes meta a mixture of clash, v2ray, and sing-box. As for looking up, you can try geo developed by Metacubex org.
An hindsight: now mihomo has supported upgrading geox (see #857) and some gui client has followed, while the guide provides an example for rule-set preferers - and it nerves geox rule users like me. Rome wasnt built in one day, especially when there is great legacy of clash (and its gui clients, say, cfw and cfa).
Verify steps
Description
Clash.Meta supports v2ray-format geosite rules, and so many examples are using geosite instead of rule-providers. Also, meta provides its own dat file at MetaCubeX/meta-rules-dat.
But as a user from Dreamacro clash, I found that
geosite.dat
has many disadvantages:geosite.dat
, but merely give examples and descriptions in README. This is extremely confusing, and one can only write rules by referring to existing examples and guessing on his own.Possible Solution
Considering the issues stated above, I'm confused that why geosite is used so widely in meta. In my opinion, the only possible explanation is that the wide-range usage of geosite in v2ray series can help reduceing maintenance pressure of clash rules.
My proposed solution to this problem is: To convert the existing geosite data source into clash text-format rules with github actions, and then release rule-providers, which can solve the current lack of well-maintained clash rules and avoid the drawbacks of geosite.