Go proxy 'searxng-gateway' adds fallback, circuit breakers, and caching to SearXNG

·4 views

A developer has released searxng-gateway, an open-source Go HTTP proxy that sits in front of SearXNG to address reliability gaps in self-hosted search. The tool adds multi-provider fallback support across Brave, Exa, Jina, and Tavily, along with per-engine circuit breakers that isolate failing backends for five minutes before attempting recovery. It runs SearXNG and a configurable set of premium providers concurrently, then falls back to remaining providers in round-robin fashion if results fall below a set threshold. An in-memory LRU cache, Prometheus metrics, and a Grafana dashboard are also included, and the proxy preserves SearXNG's existing JSON response shape so clients require no changes. The project is available under the MIT licence at version 2.6.3 on GitHub and supports a keyless mode that relies solely on SearXNG's free engines.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Python Variables, Data Types, and Input Handling Explained for Data Analysis

A foundational guide to Python for data analysis covers how variables are defined, named, and used to store and reuse data throughout a program. Python supports several data types — including strings, integers, lists, and dictionaries — and a variable can hold only one type at a time. User input can be collected via the input() function, though it stores all data as strings by default. To handle numeric input correctly, developers can use type casting to convert a variable from one data type to another, such as converting a string to an integer using int(). Understanding these core concepts is considered essential before performing any meaningful data analysis in Python.

0 comments Read more at DEV Community

ProgrammingHacker News ·

Claude Code adds fallback support for AGENTS.md when Claude.md is absent

Anthropic has updated Claude Code to recognize AGENTS.md as a fallback configuration file when no Claude.md file is present in a project. This change improves interoperability, allowing developers who already use AGENTS.md — a format associated with other AI coding agents — to work with Claude Code without creating a separate configuration file. The update was noted in the official Claude Code changelog. The move reflects a broader trend of AI coding tools accommodating shared or cross-platform configuration standards.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

wardcat: Open-Source On-Premise Data Privacy Tool for LLM and RAG Pipelines

A developer has released wardcat, an open-source Python library on PyPI designed to prevent sensitive data leaks when using large language models and RAG pipelines entirely on-premise. The tool uses a hybrid layered architecture combining Regex, SpaCy NER, and local open-weights LLMs such as Qwen3:14b to detect and anonymize sensitive information with high accuracy. A key feature called reversible masking allows anonymized text to be restored to its original form after LLM processing, while an is_sensitive() function filters prompts through a contextual security check before they are handled. Benchmarks comparing wardcat against Microsoft Presidio show wardcat's LLM layer achieving an F1 score of 0.920 on challenging scenarios and 88% accuracy in sensitivity classification, outperforming Presidio across all tested datasets. The project is publicly available on GitHub and PyPI, and the developer is welcoming contributions and feedback from the community.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI speeds up coding, but client delays are the real bottleneck in freelance work

A freelance web developer found that AI tools like Claude Code compressed a five-day build into a single day, yet projects still dragged on for weeks due to delays in receiving client-supplied assets. The real obstacle turned out to be vague, open-ended requests for logos, copy, and hosting credentials that clients struggled to prioritize alongside their regular jobs. The developer discovered that rewriting requests as specific, single-item tasks with clear format examples dramatically improved client response times. Limiting initial requests to only the essentials needed to start work also helped, rather than overwhelming clients with a full checklist upfront. Setting a transparent follow-up schedule from the first message — such as check-ins every Tuesday and Friday — eliminated the awkwardness of reminders and kept projects moving without friction.

0 comments Read more at DEV Community