Skip to content

Lack of transparency and purpose behind the excessively active CHEF-KOCH's HOSTS Spotify Ad-Filter List blocking non-Spotify domains #1471

@ArindamBagchi

Description

@ArindamBagchi

In case people are unaware of problematic activities of that user in the past and actions taken by Github and Gitlab:
nextdns/blocklists#105 (comment)

While his NSABlacklist still appears on nextDNS it's <> harmless due to the list having last updated in 6years ago.

But his Spotify Ad-Filter List is showing excessive activity. In the last 4hours I have noticed it has updated more times than any of the top blocklists.
I highly doubt "Spotify" ad filtering requires such frequent updates and complete blocking of .in(India) TLD. It was blocking amazon.in, theprint.in, bank.in(all banks operating in India moved to bank.in domain).

But my reason behind raising the issue in metadata is simple. The repo link listed on the privacy tab https://gitlab.com/CHEF-KOCH/cks-filterlist go nowhere. I don't agree with nextDNS decision to keep having this individual's block lists up which can be up for debate. But it's unacceptable a blocklist is allowed to update frequently without providing a transparent reference to check what is getting updated. Either this list has stealthily integrated NSABlacklist under Spotify tag, or has supremely bad logic behind it's blocking list. In either case this is malicious behavior and should either be updated with a proper link or outright removed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions