<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Searxng on Notes from the Rabbit Hole</title><link>https://magnus919.com/tags/searxng/</link><description>Recent content in Searxng on Notes from the Rabbit Hole</description><generator>Hugo</generator><language>en</language><copyright>© [Magnus Hedemark](https://github.com/magnus919)</copyright><lastBuildDate>Sat, 30 May 2026 10:00:00 -0400</lastBuildDate><atom:link href="https://magnus919.com/tags/searxng/index.xml" rel="self" type="application/rss+xml"/><item><title>The Easy Fix Maintainers Refuse to Take</title><link>https://magnus919.com/2026/05/the-easy-fix-maintainers-refuse-to-take/</link><pubDate>Sat, 30 May 2026 10:00:00 -0400</pubDate><guid>https://magnus919.com/2026/05/the-easy-fix-maintainers-refuse-to-take/</guid><description>&lt;p>I found a real bug in SearXNG&amp;rsquo;s Brave Search integration: the &lt;code>braveapi&lt;/code> engine was returning HTTP 422 errors from the API even though direct &lt;code>httpx&lt;/code> calls with the same parameters worked fine. I identified the root cause and submitted a &lt;a href="https://github.com/searxng/searxng/pull/6174">three-line pull request&lt;/a> with the fix. I disclosed in the PR that an AI agent helped draft it, as I do on all my contributions.&lt;/p>
&lt;p>The maintainer&amp;rsquo;s response was swift: &amp;ldquo;You ignored the PR template, instead you copied a lot of AI nonsense &amp;hellip; sorry, I will block you for a longer time.&amp;rdquo;&lt;/p></description></item></channel></rss>