3 ms·
I thought this is what the -site: operator was supposed to exist for? Could that perhaps be a solution client/user side?
by dvtrn 7y ago
I thought this is what the -site: operator was supposed to exist for?
Could that perhaps be a solution client/user side?
- lucb1e 7y agoYes, but adding a list of sites to remove to every single query you ever type... search engines should just remove bad sites (note: I am actually against removing Quora, this is just about the general case). Also, there is a maximum input length for some reason, so that might not actually work. ("For some reason" -- to prevent monster queries of course, but I mean, removing sites doesn't cost much computational power at all. With some literal quotes and AND/OR operators you can create short queries on which it basically times out after 5 seconds and only returns a few dozen results that it found so far, and when you reload the page, there are suddenly a lot more results. So it shouldn't be limiting input length but complexity, which it already does by timing out.)
- dvtrn 7y agoAlso, there is a maximum input length for some reason, so that might not actually work. I actually didn’t know that. My first thought was a browser add on that allows the user to blacklist domains they’d rather not see results and construct a query based upon. Seems like that moot if a sufficiently long list would result in sites being left off and end up in queries anyway. Thanks
- aendruk 7y agoGoogle itself used to provide a browser extension called "Personal Blocklist" that did this.