Explain the two stages: SearXNG queries DuckDuckGo and Brave, then Keenable fetches the top result pages. Name the SearXNG instance URL and disclose Keenable's logging, retention, processing location, and training use. Correct the claim that web search has no external dependency.
Explain the two stages: SearXNG queries DuckDuckGo and Brave, then Keenable fetches the top result pages. Name the SearXNG instance URL and disclose Keenable's logging, retention, processing location, and training use. Correct the claim that web search has no external dependency.
Explain the two stages: SearXNG queries DuckDuckGo and Brave, then Keenable fetches the top result pages. Name the SearXNG instance URL and disclose Keenable's logging, retention, processing location, and training use. Correct the claim that web search has no external dependency.
@ed — following up on this merge: we replaced the Keenable page fetch with a co-op-owned service (fetch.inference.coop, repo co-op/fetcher). It runs on our Cloudron, keeps no copy of URLs or page text, has no access log, and refuses internal addresses. The member-facing text you added has been updated in #16 (privacy §5/§7/§9, getting-started, infrastructure), and I requested you as reviewer there so the wording gets your check. The search engines (DuckDuckGo, Brave) still receive queries; only the page fetch is now ours.
@ed — following up on this merge: we replaced the Keenable page fetch with a co-op-owned service (`fetch.inference.coop`, repo `co-op/fetcher`). It runs on our Cloudron, keeps no copy of URLs or page text, has no access log, and refuses internal addresses. The member-facing text you added has been updated in **#16** (privacy §5/§7/§9, getting-started, infrastructure), and I requested you as reviewer there so the wording gets your check. The search engines (DuckDuckGo, Brave) still receive queries; only the page fetch is now ours.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Explain the two stages: SearXNG queries DuckDuckGo and Brave, then Keenable fetches the top result pages. Name the SearXNG instance URL and disclose Keenable's logging, retention, processing location, and training use. Correct the claim that web search has no external dependency.
dad815e6c5tob0edbf2c33Reviewed: claims verified against Keenable privacy/data docs; SearXNG URL and keyless path match the live config.
@ed — following up on this merge: we replaced the Keenable page fetch with a co-op-owned service (
fetch.inference.coop, repoco-op/fetcher). It runs on our Cloudron, keeps no copy of URLs or page text, has no access log, and refuses internal addresses. The member-facing text you added has been updated in #16 (privacy §5/§7/§9, getting-started, infrastructure), and I requested you as reviewer there so the wording gets your check. The search engines (DuckDuckGo, Brave) still receive queries; only the page fetch is now ours.