How ontherein/bettersearch-rules works
bettersearch-rules is a community-maintained rule-list dataset for BetterSearch and uBlacklist. Its main use is that BetterSearch checks search results against the sharded known-site list, using attached names to identify brand matches; users may separately subscribe to the lookalike list. The repository also generates the known-site shards from Wikidata and Majestic Million data, and supports community reports and appeals. Generation details come from the README and build-script excerpts; consumer behavior is documented in the README, not shown in sampled consumer code.
Main entry points: build.mjs Shard generator · lookalike.txt Lookalike rules · sites Site shards · report.yml Report template
Components 12
Rule Lists
- Lookalike rules
lookalike.txt
Known Sites
- Site shards
sites
Data Generation
- Shard generator
scripts/build.mjs
Community Review
- Report template
.github/ISSUE_TEMPLATE/report.yml - Appeal template
.github/ISSUE_TEMPLATE/appeal.yml
Other components
- Search user
- BetterSearch
- uBlacklist
- Wikidata
- Majestic Million
- Community reporter
- Site owner
Connections 10
- Search user → BetterSearch: searches with
README.md - BetterSearch → Site shards: checks results
README.md - BetterSearch → Lookalike rules: uses rules
README.md - Search user → uBlacklist: subscribes in
README.md - uBlacklist → Lookalike rules: reads list
README.md - Wikidata → Shard generator: provides domains
scripts/build.mjs - Majestic Million → Shard generator: provides domains
scripts/build.mjs - Shard generator → Site shards: writes shards
scripts/build.mjs - Community reporter → Report template: submits report
README.md - Site owner → Appeal template: submits appeal
README.md