Just a few minutes ago I dared to do a google search and Google refused to show me results because apparently my iPhone with latest iOS seems like an “automated search”.
Nice signal for lack of dominant AI use, it seems :D
https://github.com/verdverm/gmd/blob/main/pkg/web/providers/...
- https://github.com/MikeLuu99/searxng-rust/graphs/contributor... (as of 2026-08-03)
Though without actually checking out the source code, I believe it initially suggests respect, trust, and heartfelt gratitude towards the author, their experience, and the attitude the author bases on their miracle to be inscribed in the infinite history we all participate in...
Thank you, dear MikeLuu99, for you actually developing, being an actual developer, and the art... you do...
I wish you safety, prosperity, stability... and to your project to be acknowledged, receive enough attention, and to successfully set itself as a miracle to cherish...
There's no "religion" nor "subjectivity" here, and I have no issues with any developer who uses LLM for reviewing and auditing if they have no time or don't know anyone nor participate in Communities who will support a project in the subjects required.
If you still develop with your mind, accoutnability, creativity, and effort towards actually learning, getting valuable experience, and always prioritize a human, art, and effort, you should better know when use an LLM and when not, considering an undefined magnitude of marvelous knowledge, people, and experience you will definitely miss meanwhile, possibly remembering nothing and have no idea what you're doing at all alongside the non-accountable and prone to nonsense algorithm as LLM.
For example, if you do not consider the meat-ground miracles and artworks inside a yet another "free"/sold LLM dataset of now defaced/unknown artists, developers, engineers mentioned, people (like you and me), then if you prompt for a case to audit, require all sources to the evidence/suggestions found, carefully read the output, and manually approach it making notes to learn from and base your future on, it still may be considered an accountable development process.
I am the original author of Searx. I'm working on a new search project, Hister with a similar motivation: reducing our dependence on external search engines while keeping searches and personal data under our control.
Searx is a metasearch engine that forwards queries to other search providers. Hister takes a different approach. It builds a private full text index from content you choose, then searches that index entirely on your own infrastructure.
Hister can automatically index pages through its Firefox and Chrome extensions. It can also watch local directories, import browser history and bookmarks, index individual URLs, and crawl complete documentation sites.
The feature I find most useful is offline previews. Hister stores the readable content and HTML of indexed pages locally. You can open a result in a clean and sanitized preview beside the search results without visiting the original website again.
Some other features:
- Full text search across web pages, PDFs, docx files, Markdown, OrgMode and text files
- Phrase searches, field filters, date filters, wildcards, negation, aliases, labels, facets, and result priorities
- Optional semantic search using an embeddings endpoint you configure
- Persistent website crawls
- Imports from browser history, Linkwarden, Karakeep, Shaarli, Wallabag, and Linkding
- Web, terminal, command line, HTTP API, and MCP interfaces
- SQLite and PostgreSQL support, plus optional multiple user hosting
Hister cannot replace a global search engine (yet) for subjects you have never encountered because it only searches what you have indexed. My workflow is to search Hister first, then use its shortcut to fall back to traditional search like Searx when I need broader web results.
The project is free software under the AGPLv3+ license. It can be installed as a standalone binary or with Docker.
Project: https://github.com/asciimoo/hister
Website and documentation: https://hister.org/
Small read-only demo: https://demo.hister.org/
---
Btw, this rust implementation looks clean at first glance. The engine interface is simple enough to allow rapid engine development - which is probably the most important factor in a metasearch project.