AdBlock_Rule_For_Clash

What the rule set blocks

AdBlock Rule For Clash is a collection of domain blocking rules written for the Clash proxy client. The README describes it as an advertising domain interception rule set for Clash, and the English project title frames it as an ad block rule for Clash. The stated purpose is to reject requests to advertising domains so that they do not load through the client. The repository description adds that it targets both the premium core and the mihomo core of Clash, which are two implementations of the same proxy engine, so the rules are meant to work across those variants rather than a single build. The README does not enumerate the specific domains or the upstream sources it aggregates, so the exact coverage is defined by the generated files rather than described in prose. What is clear is the intent: filter out ad related network traffic at the proxy layer. This is a different goal from a circumvention config, because the rules are about suppressing ad domains, not about routing around network restrictions. The project carries two license badges, GPL v3 and CC BY-NC-SA 4.0, which together tell a user how the code and the content may be reused. The non commercial clause in the second license is worth noting for anyone who plans to redistribute the list as part of a commercial product, since the content license restricts that use even though the code license is more permissive. The rules are applied as reject entries, so a matching request returns nothing instead of reaching the advertiser.

Subscription formats available

The README presents a link table with three formats, and each format has three mirrored download locations. The formats are YAML, MRS, and TXT. The YAML file is named adblock_reject.yaml, the MRS file is adblock_reject.mrs, and the TXT file is adblock_reject.txt. For every format the project offers a GitHub raw link, a jsDelivr accelerated link, and a Statically accelerated link. The GitHub raw link points at the main branch of the repository, while the two CDN links pull the same file through jsDelivr and Statically respectively. Offering three formats matters because different Clash setups consume different rule encodings. YAML is the native configuration language Clash uses for rule providers, MRS is a compiled binary rule format that Clash can load quickly, and TXT is a plain list that other tools or manual setups can read. Providing both CDN mirrors alongside the raw GitHub link gives users alternatives when one host is slow or blocked in their region. The README keeps the table simple and does not explain how to wire a link into a Clash config, so a user applies the subscription by adding the chosen URL as a rule provider or reject list in their own configuration. The file names are consistent across formats, which makes it easy to swap one source for another without changing the rest of a setup. A sample configuration in the README shows a rule provider named adblock with type http, behavior classical, an interval of 120, and a timeout of 30, plus two reject rules that use GEOSITE category-ads-all and the RULE-SET named adblock.

How the list is refreshed

The project emphasizes freshness. The repository description states the rule set updates every 20 minutes, and the README carries a last commit badge that reads today, signaling that the repository is actively maintained and that new builds land on a near daily basis at minimum. A frequently rebuilt list is useful for an ad blocker because advertising domains and the infrastructure behind them change often, and a stale list lets new trackers through. The README does not describe the automation that produces the updates, so the mechanism is not something a reader can learn from the text alone. What the reader can observe is the cadence through the commit history and the badge. The dual CDN mirrors also help with freshness in practice, because a user subscribed through jsDelivr or Statically receives the latest published file without needing to watch the GitHub repository directly. Because the list is generated and pushed on a schedule, a subscriber's client simply pulls the current file at its own interval. The combination of a short update window and mirrored delivery is the project's main reliability story, even though the generation logic itself is not documented in the excerpt provided. The sample configuration sets the rule provider interval to 120 seconds, so the local client rechecks the source twice per minute and stays close to the published schedule.

Editorial conclusion

The project is dual licensed under GPL v3 and CC BY-NC-SA 4.0 and publishes rule files named adblock_reject in YAML, MRS, and TXT forms. The README states the list is rebuilt every 20 minutes and the last commit badge reads today.