-
Notifications
You must be signed in to change notification settings - Fork 101
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
✨ More upstream search engines for the websurfx
search engine
#313
Labels
Milestone
Comments
The issue has been unlocked and is now ready for dev. If you would like to work on this issue, you can comment to have it assigned to you. You can learn more in our contributing guide https://github.com/neon-mmd/websurfx/blob/rolling/CONTRIBUTING.md |
Stale issue message |
github-project-automation
bot
moved this from In Progress
to Done
in Task list for v2.0.0 release cycle
Sep 5, 2024
github-project-automation
bot
moved this from Done
to Todo
in Task list for v2.0.0 release cycle
Sep 7, 2024
Stale issue message |
github-project-automation
bot
moved this from Todo
to Done
in Task list for v2.0.0 release cycle
Nov 14, 2024
github-project-automation
bot
moved this from Done
to Todo
in Task list for v2.0.0 release cycle
Nov 18, 2024
Stale issue message |
github-project-automation
bot
moved this from Todo
to Done
in Task list for v2.0.0 release cycle
Jan 27, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
Provide more upstream search engines to aggregate results from so that more results could be provided by the
websurfx
search engine.The list of engines that could be included:
Startpage
for the search engine #314Mojeek
for the search engine #315Bing
for the search engine #316Qwant
for the search engine #317LibreX
for the search engine #318Brave
for the search engine #319Note
Google
search engine should not be included right now and is planned to be included in the future releases.Screenshots
No response
Do you want to work on this issue?
None
Additional information
No response
The text was updated successfully, but these errors were encountered: