# otobtc/ADhosts: A Directory for Hosts and Ad Blocking Rules > otobtc/ADhosts collects hosts files, AdGuard rules, and browser filtering lists for PC and Android users. It is a reference directory, not a documented installer or automatic rule-management client. **otobtc/ADhosts** — 手机电脑去广告 hosts&规则 PC&Android - Repository: https://github.com/otobtc/ADhosts - Stars: 1,606 · Forks: 161 - Language: Unknown - License: GPL-3.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/otobtc-adhosts ## What otobtc/ADhosts contains otobtc/ADhosts addresses a practical problem: hosts files and advertising filters are distributed through several projects and use different formats. A hosts file, an AdGuard rule list, a Koolproxy rule, and an Adblock Plus subscription are not interchangeable merely because all relate to advertising or tracking. This repository groups URLs by format and stated purpose instead of providing one unified filtering application. The hosts category includes yhosts, 大圣净化, 1024_hosts, AdAway, Hblock, Mvps, YousList, StevenBlack, and Google hosts. The README describes these sources as targeting domestic websites, Chinese video services, English-language advertising, Korean websites, foreign websites, tracking and malware, or website access speed. This range gives users a basis for comparison, but it also means the directory does not define one universal blocking policy. The repository also links to routing rules for Koolproxy and Adbyby, AdGuard rule lists, and subscriptions intended for Adblock Plus, Adblock, and uBlock Origin. These are external sources rather than features implemented by ADhosts. Based on the repository layout, which includes README.md, hosts, LICENSE, and .gitignore, the project is a source collection rather than a packaged PC or Android application. ## Hosts and browser rules require different integrations The hosts category belongs at the operating-system network name-resolution layer, while the AdGuard, ABP, ADB, and ubo entries are rule formats intended for filtering clients. The README does not explain whether the repository's top-level hosts file combines entries from all listed sources. It also provides no merge order, generation timestamp, or conflict policy. A user therefore cannot infer the complete contents or update behavior of that file from the URL directory alone. The linked hosts sources have different stated scopes. AdAway is identified as the official AdAway source. Hblock is described as a combined source for advertising, tracking, and malware. Mvps is associated with English-language advertising in Europe and the United States. StevenBlack is described as a multi-source collection focused on foreign websites, while Google hosts is presented as a source for improving website access speed. This list mixes content filtering, aggregation, and access-oriented sources. The browser-filter section names 乘风, anti-AD, EasyList, EasyPrivacy, EasyList China, CJX's Annoyance List, I don't care about cookies, and Adblock Warning Removal List. The README describes them as general filters, supplements, privacy lists, Chinese-language additions, and targeted warning filters. It does not say that they should all be enabled together. Compatibility and overlap remain the user's responsibility because the project provides no tested client configuration. ## PC and Android installation is not documented The README does not provide installation commands, an application package, a supported operating-system procedure, or an Android-specific setup guide. It points readers to the GitHub repository and lists external source URLs, but it does not explain how to copy the repository's hosts file onto a PC or Android device. No verified command sequence can therefore be given for installing ADhosts. The documented first-use path is indirect. A user can select one of the listed URLs and use it with a compatible hosts-based system or filtering client. However, the README does not state whether a client can subscribe directly to the otobtc/ADhosts repository's hosts entry. It also does not say whether the top-level hosts file is intended for manual copying or automatic retrieval. For rule-based clients, the README names AdGuard and the Adblock Plus, Adblock, and uBlock Origin family as audiences for several entries. It supplies no client configuration file or import command. Before applying a URL, check that it contains the expected rule format and that the chosen client accepts that format. This reflects missing documentation, not a claim that the listed rules are unusable. ## Selecting a specialized routing or browser list The README offers enough information to distinguish some list purposes, but not enough to produce a complete client setup. The AdGuard entries include a general rule from 乘风, anti-AD, EasyPrivacy, ADgk, and a halflife entry shown as deleted. Because the deletion appears in the README, the halflife URL should not be treated as an active recommendation. The project does not explain whether the remaining lists should be combined, ordered, or enabled separately. The ABP, ADB, and ubo section describes EasyList as covering English and international advertising, EasyPrivacy as addressing tracking, and EasyList China as a Chinese-language supplement. CJX's Annoyance List is described as a supplement. The cookie list and Adblock Warning Removal List target particular warnings. These are separate filtering goals, and the README does not define a recommended bundle. The routing section is more specialized still. Koolproxy links include video, daily, static, and custom-rule files. Adbyby links include xwhyc-rules, video, and lazy rules. The README does not define the syntax of the custom-rule file, explain how daily rules change, or confirm which router software accepts these formats. A router deployment needs client and format verification before an imported rule can be considered functional. ## The reference-list model leaves recovery undocumented The main limitation is that ADhosts does not present itself as a complete blocking client. The README documents no interface, Android app, desktop installer, browser extension, update daemon, or conflict detector. Its primary role is an index of external URLs. This makes it useful for finding candidate sources, but it also leaves selection, integration, and troubleshooting to the user. The README also does not document update behavior for linked resources. ADhosts was not archived, and the last push was on 2026-09-01. There are no GitHub releases listed. The README does not say how often external URLs are checked, how stale entries are removed, or whether consumers receive automatic updates from this repository. Depending on the selected link, a user may need to track both ADhosts and the separate source project. No rollback procedure is documented. If a hosts change breaks a site or a filter blocks something unexpectedly, the README does not explain how to restore a previous file, remove one source, or attribute the problem to a specific list. The README names three ad blocking test sites, but it does not link those tests to a diagnostic or recovery workflow. This is a material operational gap for a repository intended for both PC and Android use. ## ADhosts and dedicated blocking clients use different models ADhosts follows a directory model. It records links to several independent hosts files and filtering-rule lists. A dedicated client, such as one of the products named in the README, supplies the environment in which a hosts file or rule list can be applied and updated. The difference goes beyond packaging: ADhosts leaves the user to identify and combine sources, while a dedicated client may own more of the subscription workflow. The README names AdAway among hosts sources and AdGuard, Adblock Plus, Adblock, and uBlock Origin among rule consumers. It does not claim that ADhosts integrates with all of them or that its repository hosts file is generated from any one project. ADhosts is therefore better understood as a map of options than as a replacement for those clients. The platform reference also requires care. The repository description refers to PCs and Android devices, yet the README offers no platform-specific installation path. A user who needs one documented subscription workflow may be better served by a named client. A user who wants to inspect several independent source categories may find the ADhosts directory more useful. ADhosts cannot be selected safely without checking the target platform's configuration mechanism. ## GPL-3.0 and maintenance leave dependency questions The repository is identified as licensed under GPL-3.0. The README does not explain whether that license covers modifications to ADhosts alone or also applies to every external hosts file and rule list linked from it. External resources may have separate terms and update conditions. The repository's license file identifies the project's stated licensing choice, but it does not establish the licensing status of resources hosted elsewhere. ADhosts is not archived, and its last push was on 2026-09-01. No GitHub releases are listed. The README describes no versioned release process, changelog, or migration procedure. Consumers should not assume that every linked URL will remain at the same path or preserve the same contents. A direct application also creates an operational dependency on the external project, whose maintenance schedule is not described here. The repository is GPL-3.0, and redistribution or modification should be assessed against the actual license file rather than assumptions about third-party lists. No legal conclusion can be drawn from the README because it contains no licensing discussion for linked sources. The practical project-specific judgement is narrower: verify both the destination URL and its current ownership before building an update workflow around ADhosts. ## Conclusion otobtc/ADhosts suits users who understand hosts files, filtering-rule syntax, and client compatibility and want a directory of external sources. It does not suit someone seeking a ready-made PC or Android blocker, because the README documents no installer, synchronization service, or rollback procedure. Verify the selected rule URL, its compatibility with the intended client, and the effects of its entries first. ## FAQ ### Does otobtc/ADhosts provide an Android app or desktop installer? No. The README lists hosts and rule URLs for PC and Android use, but it does not document an Android app, desktop installer, or installation command. ### Can I use URLs from otobtc/ADhosts with AdGuard or uBlock Origin? The README identifies AdGuard and the Adblock Plus, Adblock, and uBlock Origin family as audiences for several rule entries. It does not provide a client-specific configuration or import procedure. ### Does otobtc/ADhosts update its hosts file automatically? The README does not document automatic updates, update frequency, or a synchronization process for the repository's hosts file. The last push was on 2026-09-01, and no GitHub releases are listed. ## Sources - [Issues](https://github.com/otobtc/ADhosts/issues) - [License: GPL-3.0](https://github.com/otobtc/ADhosts/blob/master/LICENSE) - [otobtc/ADhosts on GitHub](https://github.com/otobtc/ADhosts) - [README](https://github.com/otobtc/ADhosts/blob/master/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/otobtc-adhosts