Clearnet (SearXNG)

Loogo's clearnet layer aggregates results from the open web using SearXNG — the same architectural pattern as DuckDuckGo and Startpage, but operated as Empoorio community infrastructure.

Design

• Multiple SearXNG nodes — no single point of failure
• HTTP/JSON integration from the loogo_search Rust crate
• HTTPS mandatory for all clearnet endpoints
• Fallback chain when a node is unreachable

Provider trait

Loogo uses a unified Provider trait in the monorepo:

// Conceptual — see Plan_ejecución_Loogo_Search/00_LOOGO_ARQUITECTURA
trait SearchProvider {
    fn query(&self, q: &str) -> Result<Vec<SearchResult>>;
}

Clearnet providers wrap SearXNG instances. Web3 providers use Tantivy. The merge layer combines both.

Privacy

• Queries are not logged for advertising profiles
• No Empoorio user analytics on search content
• Node operators see aggregated uptime metrics only (internal loogo-status page)

Multi-node roadmap

Phase	Goal
1.1	Single test SearXNG instance — validate HTTP/JSON integration
1.2	Configurable node list in browser settings
1.3	Community node registry on EmpoorioChain
1.4	DMS rewards for nodes meeting uptime SLOs

Fallback behavior

If all SearXNG nodes fail, the omnibox falls back to the configured legacy engine (DuckDuckGo during transition) — search never hard-fails for the user.