Documentation for MiniSearch
OpenSearch description format - XML | MDN
The OpenSearch description format can be used to describe the web interface of a search engine. This allows a website to describe a search engine for itself, so that a browser or other client application can use that search engine. OpenSearch is supported by (at least) Firefox, Edge, Safari, and Chrome. (See Reference Material for links to other browsers' documentation.)
The Magic of Small Databases
Notes on personal libraries, collections and small indexes on the web
Full bibliography | STEEP DMAC Tracker
The search interface is made of three sections: Search, Explore, and Results. These are described in detail below.
2025-0915_OP-MiniWS-r4.pdf
Standard Search
A search engine for standard.site posts, indexing documents published on AT Protocol.
🔎 supabase custom aws - Google Search
Introduction
A complete search engine and RAG pipeline in your browser, server or edge network with support for full-text, vector, and hybrid search in less than 2kb.
tobi/qmd
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
Paper page - Knowledge Navigator: LLM-guided Browsing Framework for Exploratory Search in Scientific Literature
Join the discussion on this paper page
Thoughts on Algolia (vs Solr & Elasticsearch) - OpenSource Connections
In this blog, we discuss our thoughts on Algolia versus Solr and Elasticsearch.
New demo version of atsearch.network is here 💃 quick recap: any AT Proto app can invent its own record type: scrobbles, books, photos, RPGs, etc... nothing searches across them so i built a search engine that reads your lexicon and figures out how to index you
New demo version of atsearch.network is here 💃 quick recap: any AT Proto app can invent its own record type: scrobbles, books, photos, RPGs, etc... nothing searches across them so i built a search engine that reads your lexicon and figures out how to index you
We talk a lot about how the Discovery algorithm can be improved for users.... I would like to add that *search* is also a core UX that needs help. Searches always seek new, relevant results—so "Top" and "Latest" are both wrong. I need closer to "Top latest" cc cc @alexbenzer.com @toni.bsky.team
