Ive been using brave for years now with very few issues with it, but there is one issue which i hate they implemented, and that is when you use search operators on a uncommon search, brave just says “search operators were not applied, Too few matches were found”, and then searches without the operators, and what annoys me more is that when i use the exact same search on a different browser like google chrome, it gives me some results with the search operators, considering both brave and google chrome both use chromium, they should come up with the same results (i think).
what i want is a way to enable a way to force use search operators, even if brave deems it to get “too few results”.
4 Likes
Very much absolutely ridiculous why it won’t let you override that. Don’t say “Too few”, either say “None found” or show me the results. I’m using search operators to find exactly what I’m looking for so I SHOULD find less results. I EXPECT less results. You tell me there’s “too few results”, literally the entire purpose of me using the operators in the first place, and refuse to show me them? Does this team understand how incredibly frustrating that is to a user?
Especially when I can plainly prove it wrong by simply using another search engine and getting 2 whole pages of results. Which almost exactly match the results of the first 2 of 100 pages Brave gives me when I instead just take out the operators and add a related keyword I know exists. I would rather Brave give me the 2 pages of “too few results”, or just the 5 results it found.
Because otherwise this is legitimately a bug or issue with the most basic ““ search operator. It’s failing to find exact phrases from results it can otherwise find and reference all the text of in general search. The way this actually feels to work is that the engine is unwilling or unable to process website text comprehensively to find these exact phrases and just gives up before it even tries.
1 Like
In my honest experience as a user who’s been frustrated by it, when it says that, what it means is, it actually had “zero” results in it’s database.
It’s why I enabled the Google fallback, so it does forward these to pull in more and train Brave search for those edge cases.
This setting usually helps with that.
I used to think it stunk there wasn’t an override, until I started to realize, it really meant “no matches”, not “too few”. Perhaps poor verbiage.
