mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #97] [FEATURE] Block results from useless websites #69
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#69
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @grigsby on GitHub (Jul 4, 2020).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/97
Describe the feature you'd like to see added
The ability to maintain a blocklist of websites you never want to see results from. Inspired by browser add-ons such as Unpinterested! and uBlacklist that allow you to block search results from (e.g.) Pinterest.
Describe which parts of the project this would modify (front end/back end/configuration/etc)
Sorry, I don't know.
Additional context
Google image search results prominently feature Pinterest, but those results are pretty useless since Pinterest requires creating an account and logging in before being able to view pages. It would be nice to have the ability in Whoogle search to block all results from these types of useless websites. uBlacklist (browser extension) works great when searching directly with Google, but has no effect when searches are proxied through Whoogle.
@dmytro-shchurov commented on GitHub (Jul 20, 2020):
This would be great. Google is full of Q&A websites, that display Google's ads after each 10 rows of text, and block accessing their sites without accepting marketing cookies.
@ghost commented on GitHub (Apr 12, 2021):
This would be an awesome feature indeed. I've been experimenting with addons like uBlacklist and with client-side javascripts like this one. Up to a point those tend to work, but they all tend to break very often too. IMO the most reliable and resource-friendly way to implement this is by using the existing search operators, especially
-site:foo. That would avoid any overhead caused by potentially having to soup a lot of stuff out of a search resultset. If anyone knows how to add such a string to the search query in the whoogle code base, that would be golden!