deploy: ship the search block, so the live web is on for this box
Owner's call. The code default stays off — no `search` block still means no query leaves the LAN — but the deployed config now carries one, so a question that is not about him reaches SearXNG before it reaches the ZIMs. Nothing runs at http://searxng:8080 on homesrv yet. That is the designed degradation and not a broken turn: an unreachable instance falls through to Kiwix and she never says the search failed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
@@ -195,7 +195,9 @@ world questions, so she needs to read external sources. What replaces it:
|
||||
2026-08-02). A self-hosted SearXNG (`search` block) answers first; the Kiwix ZIMs on
|
||||
homesrv answer when the search is empty, unreachable, or the line is down.
|
||||
- **External search is allowed and off unless configured**, like the weather and telegram
|
||||
capabilities.
|
||||
capabilities. The code default is still off. `deploy/mavend.json` now ships a `search`
|
||||
block (owner's call, 2026-08-02), so it is on for this box and deleting the block turns
|
||||
it off again.
|
||||
- **His notes and facts are never search input.** Looking up why the sky is blue and sending
|
||||
his stored personal notes to an upstream engine are different acts. Only the utterance goes
|
||||
out, never the persona block, history, or matched notes.
|
||||
|
||||
Reference in New Issue
Block a user