You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I've noticed that refreshing the page - hence making the same question again - produces different results. Making the search engine less reliable as you don't know if the first answer is the correct one.
To Reproduce
make a search, wait for the result, refresh the page.
Expected behavior
The answer while not exactly the same in terms of wording when refreshing the page, should contain the same information in a consistent way.
Screenshots
I apologise for the load of screenshot, but it's the best way to explain this issue.
Additional context
None
The text was updated successfully, but these errors were encountered:
I have encountered this as well about 5% of the time. You see some of the times the responses have sources (often good quality responses) and sometimes it doesn't have sources displayed and those are far more questionable quality wise. I wonder if is SearxNG's fault or somehow the backend is not using it correctly. In my brain, ideally Perplexica would breakdown multi-part questions into smaller more searchable questions, then retrieve those text, run embedding on those texts and then again recombined all of them using LLM. Any clarifications from the repo owner is welcomed.
Very low confidence guess it can be related to this error as well: #292
Describe the bug
I've noticed that refreshing the page - hence making the same question again - produces different results. Making the search engine less reliable as you don't know if the first answer is the correct one.
To Reproduce
make a search, wait for the result, refresh the page.
Expected behavior
The answer while not exactly the same in terms of wording when refreshing the page, should contain the same information in a consistent way.
Screenshots
I apologise for the load of screenshot, but it's the best way to explain this issue.
Additional context
None
The text was updated successfully, but these errors were encountered: