Spaces:
Running on Zero
Running on Zero
Commit History
12 days ago
-
sync: from ael backend/space/
d409fec -
sync: from ael backend/space/
558fffa -
feat(search): relevance reranking with Laya, and restore files the last commit clobbered
Adds the reranker, and puts back what 4dba37a overwrote. 4dba37a was a mistake: it synced the whole of backend/space/ over the Space, and this repo's copy of that folder is a STALE FORK. It reverted app.py's _KEY_HEADERS alias (the x-respite-key / x-ael-key fix), its _is_protected fix, the raised request_timeout in searxng_settings.yml, and the explicit mojeek/marginalia/rightdao/mwmbl/presearch engine list. Restored here from 17b0658; this commit touches only the three files it meant to. The reranker itself: - rerank.py scores each (query, passage) pair with convaiinnovations/laya, a non-autoregressive System 1 decision model (421M English / 322M multilingual, Apache-2.0), using a `noul` question for the calibrated P(yes) that the passage contains what the query needs. - The race only ever asked "is this set big enough", so the winner was whoever answered first and a small index won on speed alone. "what is the capital of Peru" came back as NPR transcripts about mummy lice…184d40c
24 days ago
-
Surface searxng bootstrap errors in status route
Buffy79019c5 -
Add SearXNG userspace runtime with DDG + Google engines
BuffyBootstrap pattern mirrors node_runtime: fetch source tarball, pip-install into a userspace venv on first boot, launch bound to 127.0.0.1:8888. FastAPI bridge exposes /respite/v2/searx/search (JSON API proxy).42f6abb