Skip to content

v1.0.0-alpha.1

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 22 Oct 22:14
· 12 commits to main since this release

Breaking

  • The default backend changes from private SearXNG to native Go metasearch.
    Set SEARCH_BACKEND=searxng to retain the previous backend. In native mode,
    CACHE_SIZE counts retained results, including frozen pages, rather than
    legacy cache entries.

Changed

  • Native Go metasearch is the default backend: direct Bing and DuckDuckGo
    images/videos, plus Wikimedia images. No AI model or separate Python search
    service is required. The existing SearXNG backend remains available with
    SEARCH_BACKEND=searxng for a compatible switchback.
  • Native inline retrieval collects a partial first page, freezes returned
    cards, and adds later results through stable opaque pagination. Telegram's
    already-answered inline picker is not updated in place. DM/group grids and
    owner-bound Vido delivery keep their existing behavior.
  • f: explicitly selects the same fast, non-AI search as an ordinary query.
    Combine it with i: or v: in either order, including in /search.
  • Native search defaults to an 800ms first-page collection window and 3.5s
    source budget, with up to eight concurrent searches. Optional SearXNG fallback
    stays within the overall 8s request budget; SEARCH_FALLBACK=none disables
    it. These are operating budgets, not measured production latency guarantees.
  • Result caches and pagination sessions are bounded in memory with a default
    five-minute TTL. Raw query text stays out of sessions, logs, and databases;
    partial/degraded responses are not cached as complete healthy results.
  • Local Compose retains private SearXNG for fallback and rollback without public
    ports. Native-only startup can run just the bot. Search needs no new database.

Known Limitations

  • This alpha is intended for owner-directed testing on the primary Searchy
    instance. Actual Telegram inline/media delivery and the full Vido delivery
    matrix remain to be verified after rollout; CI and mocked integration tests
    do not prove those live flows.
  • DuckDuckGo Images can return an HTTP 202 challenge. Other native sources can
    still produce partial results; the optional private SearXNG fallback covers
    weak or empty initial retrieval within the overall search budget.

Container image

ghcr.io/freshlabdev/searchy@sha256:8356b191b657e87b2aaee5104c9850a6bbc36c395ebc67f7600216237053ba80