Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yahoo blocked #460

Closed
kashmirix opened this issue Jan 21, 2024 · 10 comments · May be fixed by #496
Closed

Yahoo blocked #460

kashmirix opened this issue Jan 21, 2024 · 10 comments · May be fixed by #496
Labels

Comments

@kashmirix
Copy link

The last update blocked all Yahoo! services by adding the naked domain yahoo.com in Hosts/GoodbyeAds.txt. This needs to be reverted asap.

@Deathbyteacup
Copy link

Yep. Recent updates have just been blanket banning all kinds of legitimate websites. I won't be using this list again; highly reckless behaviour.

@naturalpb
Copy link
Contributor

I disabled the "Goodbye Ads" filter in my NextDNS because of this issue. I agree that blocking yahoo.com in full is unacceptable and hope it's corrected soon.

@netahoy
Copy link

netahoy commented Jan 25, 2024

four whole days and yet no action..... are we hitting the breakpoint?

@aLostEngineer
Copy link

aLostEngineer commented Mar 11, 2024

Almost 2 months and NOTHING. This list is abandonware and I'm removing it from NextDNS. @jerryn70 how about addressing user complaints and NOT blocking entire swaths of the internet? just a thought since your list increasingly SUCKS recently.

Edit: I have requested NextDNS remove this list from the suggested blocklists due to erroneous and prejudicial blocking.

@jerryn70
Copy link
Owner

Fixed

@naturalpb
Copy link
Contributor

@jerryn70 I'm glad that you fixed this particular issue, but I am concerned that it took 1.5 months to correct it after causing significant issues for users of the list. I'm unwilling to trust using this list again unless guarantees are made about future support.

@Deathbyteacup
Copy link

Yep, too little, too late - completely reckless behaviour, and a completely unacceptable response / time to respond. List is completely untrustworthy, and should be closed.

@aLostEngineer
Copy link

Yep, too little, too late - completely reckless behaviour, and a completely unacceptable response / time to respond. List is completely untrustworthy, and should be closed.

I fully support the closure of this list due to negligence, poor response time, and blatant disregard for customer needs.

@kashmirix
Copy link
Author

kashmirix commented Mar 12, 2024

Yep. Introducing untested changes that significantly affect unintended targets and then disregarding immediate multiple notifications from users is not a way to develop this type of software, even if it's free. I also support removal.

@ispiropoulos
Copy link

The yahoo.com entry remained in the filter file. This MR resolves the issue. @jerryn70 can you please merge?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants