# Profiles4limbo: A Quantumult X Lazy Config for Ad Blocking and TikTok Unblocking > Profiles4limbo is a prebuilt Quantumult X configuration file that wires up ad-blocking rules, TikTok and VSCO rewrites, and per-app policy groups. It is aimed at iOS users who want a working proxy setup without assembling rules by hand, and its main constraint is that it depends on several third-party rule repositories, some of which have stopped updating. **limbopro/Profiles4limbo** — 毒奶自用，懒人配置文件（Quantumult X）：去广告分流规则、Tiktok解锁重写、VSCO解锁、神机分流、blackmatrix7分流规则。 - Repository: https://github.com/limbopro/Profiles4limbo - Stars: 3,518 · Forks: 242 - Language: JavaScript - License: not declared - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/limbopro-profiles4limbo ## What Profiles4limbo Actually Assembles Quantumult X is a rule-based proxy client for iOS. Out of the box it does nothing useful for a new user: you have to define policy groups, point them at rule lists, and decide which traffic goes where. Profiles4limbo is a single configuration file, full.conf, that does that assembly in advance. The README calls it a lazy one-click config, and the repository description says it is for personal use. The audience is narrow and specific. You need Quantumult X already installed, you need at least one airport subscription (the Chinese term for a commercial proxy subscription), and you want the common cases handled: blocking ads, routing Apple services directly, sending AI platform domains through a proxy, and unlocking TikTok. If you are comfortable writing your own Quantumult X config, this project saves you an afternoon but adds a dependency you do not control. The repository also carries a Surge directory for Surge users who do not want to use a subscription conversion API, plus standalone files named tiktok.conf, vsco_crack.conf, adobecc.list, Netflix/, UNBLOCK/, and AI_Platforms.list alongside AI_Platforms_qx.list. The .list files are rule lists; the .conf files are rewrite configurations. ## Policy Groups, Rule Lists and the Filter Chain The mechanism is Quantumult X's own config format, not custom code. full.conf has a [policy] block that declares the groups, a [filter_remote] block that pulls rule lists from URLs and forces matched traffic into a named group, and a [rewrite_remote] block that pulls script-based rewrites. The [policy] block defines groups including the ad-block group, the failover group, the airport group, the Apple group, the AI Platforms group, and the Netflix, Disney+, TikTok and Final groups. Each line lists the candidate policies in priority order. The ad-block group, for example, is declared as REJECT, PROXY, DIRECT, so the first choice is to reject the request. The README warns that ad blocking can cause errors and says the fix is to change the ad-block policy preference to PROXY or Direct. The failover group is the interesting one. The README states it automatically checks the nodes selected under that group from top to bottom and switches to an available one. Surge, by contrast, switches to the lowest-latency node. That difference matters if you care about latency rather than mere availability. Traffic classification comes almost entirely from external lists. The [filter_remote] block points at blackmatrix7's ios_rule_script repository for Netflix, Disney, TikTok, Apple, OpenAI, BardAI and Claude, at limbopro's own airports.list and AI_Platforms_qx.list, and at limbopro.com/Adblock4limbo.list for web ad blocking. Each entry carries a tag and a force-policy, which is what binds a list to a group. Remove a line and that app falls through to the next matching rule, ultimately to Final. ## Installing full.conf and Getting a First Working Setup The README gives the install path as a URL download inside the app. Copy the raw link to full.conf, open Quantumult X, tap the settings button in the bottom right, find the 配置文件 module, tap 下载, paste the link, and confirm. The README says eight policy groups appear afterward. Note that the README elsewhere says ten policies in the preview image and eight after the operation, so the count is not stated consistently. ```bash https://raw.githubusercontent.com/limbopro/Profiles4limbo/main/full.conf ``` If the app reports 无效的自变量 (invalid argument) during download, the README attributes it to the phone being unable to reach raw.githubusercontent.com and suggests opening the same URL in a mobile browser to confirm. The documented workaround is to copy the contents of full.conf and paste them into the config editor manually: tap the settings button, scroll to 配置文件, tap 编辑, long-press anywhere, choose 全选 then 粘贴, and save with the top-right button. After the config loads, you still have no working proxy until you add a subscription. The [server_remote] block in the published file is empty. The [server_local] block ships with placeholder entries tagged 无用节点1 and 无用节点2: ```yaml shadowsocks=example.com:80, method=aes-128-gcm, password=pwd, obfs=ws, fast-open=false, tag=无用节点1 ``` Those are placeholders, not usable nodes. The README instructs you to delete the useless nodes under the failover group and, in the same edit, add at least two nodes or the app will refuse to save. Add your own subscription under [server_remote], then assign nodes inside each policy group in the app UI. DNS is set in the [dns] block to 223.5.5.5, 114.114.114.114 and 119.29.29.29 with no-system and no-ipv6 disabled lines present. ## Where This Config Breaks or Misleads The dependency chain is the biggest risk. The README itself labels ConnersHua's 神机规则 and DivineEngine's Profiles as stopped updating, and marks NobyDa's ND-AD ad-block list as stopped after reaching a stated 10w+ figure. The current full.conf no longer references NobyDa for ad rules, pulling limbopro.com/Adblock4limbo.list and Adblock4limbo.conf instead, but the historical reliance on abandoned lists is documented in the README's own repository list. If blackmatrix7's repository changes its paths or stops publishing, every force-policy line pointing at it fails silently in the sense that the app simply has no rule to match. Ad blocking by REJECT is a blunt instrument. The README acknowledges that it can cause errors and offers the PROXY or DIRECT switch as the remedy. That is a per-user workaround, not a rule-level fix, so a site broken by an over-broad block stays broken until you flip the whole group. There is no licence file in the repository listing. The README credits upstream authors but does not state terms for the config itself, and several of the referenced rule sets carry their own conditions. That is a real gap if you plan to redistribute or bundle the file. Finally, the project is personal. The README describes it as 毒奶自用 (for the author's own use) and routes support to a Telegram channel, a Telegram group, a Telegram bot and an email address. There are no releases in the repository listing, so updates arrive as commits to main. The last push was on 2026-07-18, which is more than six months before today, so treat the file as it stands rather than expecting current maintenance. ## Profiles4limbo Versus Writing Your Own Quantumult X Config The alternative is not another product so much as the manual route: build your own Quantumult X config and subscribe directly to blackmatrix7's ios_rule_script lists. The difference is control. Profiles4limbo pre-binds each list to a named policy group and adds the airport and ad-block layers that blackmatrix7 does not provide. Doing it yourself means writing the [policy] and [filter_remote] blocks, deciding the group names, and picking the fallback order for each one. A second alternative, for Surge users, is the Surge directory in this same repository, which the README offers specifically for people who do not want to run a subscription conversion API. That is a different client with a different config grammar, so it is a migration rather than a drop-in swap. Compared with a plain blackmatrix7-based setup, Profiles4limbo adds the ad-blocking rewrite layer from limbopro.com and the airport domain routing from airports.list. It also adds the failure mode: an extra hop through a personal domain that can go down independently of the rule lists it wraps. ## Maintenance Cost, Licence Status and What to Check Upgrading means re-downloading full.conf or re-pasting its contents, which overwrites local edits to policy groups and node assignments. If you have customized the ad-block preference or added nodes, those changes are lost on refresh unless you keep a copy. The README's FAQ section mentions backing up airport subscriptions before starting, which is consistent with that risk. The [filter_remote] and [rewrite_remote] entries update independently of the config file, since Quantumult X fetches them from their source URLs. So the practical maintenance work is checking that those URLs still return content. The two limbopro.com endpoints, Adblock4limbo.list and Adblock4limbo.conf, sit on a personal domain and have no upstream mirror listed. On licensing: the repository has no licence identifier in the metadata, and the README only credits upstream projects by name and link. If you intend to redistribute the config or ship it inside another product, the absence of stated terms is something to resolve with the author before you rely on it. Nothing here constitutes legal advice; it is simply what the repository does and does not state. ## Conclusion Adopt Profiles4limbo if you already run Quantumult X on iOS, want ad-blocking plus TikTok or VSCO rewrites without writing filter lists yourself, and accept that parts of the rule chain come from repositories the README marks as stopped. Do not adopt it if you need a maintained rule set with a published licence, if you are on Android, or if you refuse to paste a config from a personal repository into your proxy client. Before trusting it, open full.conf and check each filter_remote and rewrite_remote URL, confirm which of them still resolve, and decide whether the ad-block policy should stay on REJECT or be switched to PROXY or DIRECT. ## FAQ ### How do I install Profiles4limbo in Quantumult X? Copy the raw link to full.conf, open Quantumult X, tap the settings button in the bottom right, find the 配置文件 module, tap 下载, paste the link and confirm. If the app reports 无效的自变量, the README says to open the link in a mobile browser and, if it fails, paste the file contents into the config editor manually. ### Why does my Profiles4limbo config show useless nodes? The published full.conf ships placeholder entries tagged 无用节点1 and 无用节点2 under [server_local], and the [server_remote] block is empty. You add your own subscription and assign nodes in the app. The README notes that when deleting a useless node under the failover group you must add at least two nodes or the app will not save. ### Does Profiles4limbo block ads, and can it break websites? Yes, the ad-block policy group defaults to REJECT and pulls lists from limbopro.com and blackmatrix7. The README warns that ad blocking may cause errors, and says the fix is to change the ad-block policy preference to PROXY or Direct. ### Can I use Profiles4limbo on Android or with Surge? The config is written for Quantumult X, which is an iOS client, so it does not apply to Android. The repository does include a Surge directory for Surge users who do not want to use a subscription conversion API, but that is a separate config in a different format. ### Is Profiles4limbo still being updated? The repository is not archived, but the last push was on 2026-07-18 and there are no retrieved releases. The README also marks several upstream rule sources, including ConnersHua, DivineEngine and NobyDa's ND-AD list, as stopped updating. ## Sources - [Issues](https://github.com/limbopro/Profiles4limbo/issues) - [limbopro/Profiles4limbo on GitHub](https://github.com/limbopro/Profiles4limbo) - [README](https://github.com/limbopro/Profiles4limbo/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/limbopro-profiles4limbo