From 92bc4b3cba1beb7aa443c4dcbb1e741ece3a5deb Mon Sep 17 00:00:00 2001 From: Igor Soarez Date: Mon, 3 Aug 2026 22:17:46 +0100 Subject: Record measured rate-limit behaviour per engine MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Concrete numbers from development rather than a vague warning: Google tolerates a lot then blocks for ~90 minutes, Brave challenges after one or two queries and clears in ~15-20, and DuckDuckGo and Bing never challenged at all. That last fact is the useful one — it says which engine to reach for when several searches are needed in a row. --- src/engines.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src') diff --git a/src/engines.ts b/src/engines.ts index a71b9c8..ef8baef 100644 --- a/src/engines.ts +++ b/src/engines.ts @@ -172,7 +172,7 @@ const BING: EngineDefinition = { const BRAVE: EngineDefinition = { id: "brave", label: "Brave Search", - note: "independent index and unwrapped links; challenges quickly under repeated queries", + note: "independent index, direct links; challenges after 1-2 queries, clears in ~15-20 min", // Left empty deliberately — see the note in README. Brave's filter UI is // client-rendered and the `tf=` values could not be confirmed against a page // that was not simultaneously serving a bot check, so no window is claimed -- cgit v1.3.1