[GH-ISSUE #312] Split the lists to be more extensible #212

New Issue

saavagebueno · 2026-08-06T02:13:26-04:00

saavagebueno commented

2026-08-06 02:13:26 -04:00

Originally created by @DanWaLes on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/laylavish/uBlockOrigin-HUGE-AI-Blocklist/issues/312

There's a mix of first-party AI clients and AI generated slop. Some AI models actually respect licensing terms or sought permission to scrap content before scraping.

I object the use of AI models that disrespect the author's ownership.

First-party AI clients can sometimes be useful for q/a for debugging programs, system maintenance, etc.

Originally created by @DanWaLes on GitHub (Dec 31, 2025). Original GitHub issue: https://github.com/laylavish/uBlockOrigin-HUGE-AI-Blocklist/issues/312 There's a mix of first-party AI clients and AI generated slop. Some AI models actually respect licensing terms or sought permission to scrap content before scraping. I object the use of AI models that disrespect the author's ownership. First-party AI clients can sometimes be useful for q/a for debugging programs, system maintenance, etc.

saavagebueno commented

2026-08-06 02:13:26 -04:00

@DanWaLes commented on GitHub (Jan 16, 2026):

What I mean is the hosts file needs to be better split. Hosts files work at the domain level, which can be network wide.
I see it beneficial to split into:

Integrations (like if there's an api. subdomain),
Nuclear Integrations (like if there is an api, but isn't on a dedicated subdomain)
Media sharing (domains specifically for ai "art" or "music" sharing). This list will break AI use cases, but that is fine when there are plenty of standalone apps that don't host user generated content.
NSFW AI websites
Chatbots/LLMs (ChatGPT, Grok, CharacterAI, Perplexity, etc)
AI content farms
Break websites made with AI website/cloud tools (like subdomains of Firebase used on websites)

@DanWaLes commented on GitHub (Jan 16, 2026): What I mean is the hosts file needs to be better split. Hosts files work at the domain level, which can be network wide. I see it beneficial to split into: * Integrations (like if there's an `api.` subdomain), * Nuclear Integrations (like if there is an api, but isn't on a dedicated subdomain) * Media sharing (domains specifically for ai "art" or "music" sharing). This list will break AI use cases, but that is fine when there are plenty of standalone apps that don't host user generated content. * NSFW AI websites * Chatbots/LLMs (ChatGPT, Grok, CharacterAI, Perplexity, etc) * AI content farms * Break websites made with AI website/cloud tools (like subdomains of Firebase used on websites)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: DYNR/uBlockOrigin-HUGE-AI-Blocklist#212