Max Lin

ChatGPT 走代理，
富途直连，
CSDN 直接拦掉ChatGPT through your proxy, Futu direct, CSDN blocked

按服务拆好的 Surge 和 Clash / Mihomo 分流名单。名单只写哪些域名算这个服务，走代理、直连还是拒绝，在你自己的配置里定。Routing lists for Surge and Clash / Mihomo, split by service. A list only says which domains belong to a service; whether they go through a proxy, direct or nowhere is set in your own config.

在 GitHub 上查看规则View the rules on GitHub Max Lin 手工维护，MIT 许可。不含节点，也不是订阅服务。Maintained by hand by Max Lin, MIT licensed. No proxy servers, no subscription service.

名单只管匹配，
走哪条路由你的配置定The lists only match. Your config picks the route.

每份名单只列 DOMAIN、DOMAIN-SUFFIX、DOMAIN-KEYWORD，没有策略列。Surge 里用 RULE-SET 引用，Clash / Mihomo 里作为 classical rule-provider 引用，再指向你已有的策略组、DIRECT 或 REJECT。订阅地址跟着 main 分支，文件路径保持不变。Each list holds only DOMAIN, DOMAIN-SUFFIX and DOMAIN-KEYWORD lines, with no policy column. Reference it with RULE-SET in Surge or as a classical rule provider in Clash / Mihomo, then point it at a policy group you already have, DIRECT or REJECT. Subscription URLs follow main, and file paths stay put.


    

  


  

    
22 份 Surge，21 份 Clash22 Surge lists, 21 for Clash
TikTok 暂时只有 Surge 版。同名文件之间已知的覆盖差异记在规则索引里。TikTok is Surge-only for now. Known coverage differences between same-name files are in the rule catalog.

    
手工维护Edited by hand
没有生成脚本，没有 CI 和定时同步。改动推到 main 后，刷新规则集就能拿到。No generator, no CI, no scheduled sync. Once a change is on main, refreshing the rule set picks it up.

    
AI 可以合着用One AI list, if you prefer
AI.txt 是单独维护的聚合名单，所有 AI 服务走同一个策略时用它。AI.txt is a separately maintained aggregate, for when every AI service takes the same policy.

    
附一份 Surge 基础配置A Surge base profile
base.conf 是作者自用配置的公开版，没有 [Proxy] 段，要先接上你自己的节点。base.conf is the public version of the author's own profile. It has no [Proxy] section; bring your own proxies.

  







  
  
平台Platform
Surge · Clash / Mihomo
要求Requires
Surge（iOS 或 Mac），或使用 Mihomo 内核的 Clash 客户端；一份已经能用的配置，以及你自己的节点或策略组。可选的 Surge 基础配置用到了 smart 策略组，需要 Surge iOS 5.11.0 / Mac 5.7.0 或更新版本。Surge (iOS or Mac), or a Clash client running the Mihomo core; a working configuration with your own proxies or policy groups. The optional Surge base profile uses smart groups, which need Surge iOS 5.11.0 / Mac 5.7.0 or later.
许可证License
MIT



  
常见问题Questions

  

    
Surge 怎么添加远程规则集？How do I add a remote rule set to Surge?
在配置已有的 [Rule] 段里加一行 RULE-SET,<地址>,<策略>，例如 RULE-SET,https://raw.githubusercontent.com/max1874/funnysurge/main/rules/OpenAI.txt,PROXY，把 PROXY 换成你配置里已有的策略名。这一行要排在更宽泛的规则和 FINAL 之前。保存后更新规则集，再在请求记录里看实际命中的规则和策略。Add a line RULE-SET,<url>,<policy> inside your existing [Rule] section, for example RULE-SET,https://raw.githubusercontent.com/max1874/funnysurge/main/rules/OpenAI.txt,PROXY, replacing PROXY with a policy name your profile already defines. Put it before broader rules and FINAL. Save, refresh the rule set, then check the matched rule and policy in Surge's request list.

    
在 Clash Verge Rev 或其他 Mihomo 客户端里怎么用？How do I use these rules in Clash Verge Rev or another Mihomo client?
Clash Verge Rev 内置 Mihomo 内核，配置方式与 Mihomo 相同：用 clash/ 目录下的文件地址，在 rule-providers 里加一个 type: http、behavior: classical、format: yaml 的 provider，再在 rules 里写 RULE-SET,<provider 名>,<策略>，排在宽泛规则和 MATCH 之前。这些文件扩展名是 .txt，内容是 YAML payload 列表。仓库 examples/ 里有可以直接合并的片段。Clash Verge Rev ships the Mihomo core, so the setup is the same as for Mihomo: add a provider under rule-providers with type: http, behavior: classical, format: yaml and the URL of a file from clash/, then add RULE-SET,<provider name>,<policy> to rules, before broader matches and MATCH. The files end in .txt but contain YAML payload lists. The repo's examples/ folder has a snippet ready to merge.

    
和 blackmatrix7、Loyalsoldier、Sukka 这类大型规则集有什么不同？How is this different from large community rule sets like blackmatrix7, Loyalsoldier or Sukka?
那些项目覆盖的范围大得多，其中 Loyalsoldier 和 Sukka 的规则由 GitHub Actions 每天定时构建。funnysurge 是一个人按自己的使用情况手工维护的小名单，没有生成脚本，也没有定时同步，适合补充或单独覆盖某几个服务。两者可以同时用：作者自己的 base.conf 就同时引用了这些项目的规则和本仓库的名单。Those projects cover far more ground, and Loyalsoldier's and Sukka's rules are rebuilt daily by scheduled GitHub Actions. funnysurge is a small set of lists maintained by hand around one person's usage, with no generator and no scheduled sync, which suits supplementing or overriding routing for a few specific services. They work together: the author's own base.conf references rules from those projects alongside these lists.

    
用 AI.txt 还是单个服务的名单？Should I use AI.txt or the individual service lists?
所有 AI 服务走同一个策略时用 AI.txt，覆盖面更宽；不同服务要走不同策略时用单独的名单。两者都用的话，把具体服务的规则放在前面。AI.txt 里还有共享基础设施域名和一些与 Google Gemini 无关的 Gemini 协议站点，选用前可以先看一遍内容。Use AI.txt when every AI service should take the same policy; it covers more. Use the individual lists when services need different policies. If you use both, put the specific ones first. AI.txt also includes shared infrastructure domains and some Gemini-protocol sites unrelated to Google Gemini, so it is worth reading before you choose it.

    
这里提供节点或订阅吗？Does it include proxy servers or a subscription?
不提供。这里只有规则文件、配置片段和一份基础配置，节点需要自备。规则只决定一条连接匹配到哪个策略，策略背后是什么由你的配置决定。No. The repository has rule files, configuration snippets and a base profile only; you bring your own proxies. A rule decides which policy a connection matches, and what that policy does is up to your configuration.

    
名单怎么更新？发现规则不对怎么办？How are the lists updated, and how do I report a wrong rule?
所有名单都是手工修改后推到 main，没有 CI 或定时任务；订阅地址跟随 main，在客户端刷新规则集就会拿到新内容。发现误判请在 GitHub issue 里写明域名、客户端、规则文件和期望的分流结果。Every list is edited by hand and pushed to main; there is no CI or scheduled job. Subscription URLs follow main, so refreshing the rule set in your client fetches the new version. To report a wrong match, open a GitHub issue with the domain, client, rule file and the route you expected.

  


  
获取帮助Get help

  
发邮件到Email hi@max1874.com，或在 , or open an issue on GitHub 提 issue。写上版本和运行环境，能更快定位问题。. Include the version and your environment so the problem is easier to find.