<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ai Crawlers on BareProxy.com</title>
    <link>https://bareproxy.com/tags/ai-crawlers/</link>
    <description>Recent content in Ai Crawlers on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/ai-crawlers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Plugins Go WebAssembly, Starting With RenderCache and AI Crawler Control</title>
      <link>https://bareproxy.com/bareproxy-plugins-go-webassembly-starting-with-rendercache-and-ai-crawler-control/</link>
      <pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-plugins-go-webassembly-starting-with-rendercache-and-ai-crawler-control/</guid>
      <description>&lt;p&gt;BareProxy&amp;rsquo;s core stays bare. Everything else comes as plugins, and a plugin is now a WebAssembly module that BareProxy loads at run time. That replaces the earlier plan of modules compiled into the binary.&lt;/p&gt;&#xA;&lt;p&gt;Three things change for anyone running it. A plugin is a &lt;code&gt;.wasm&lt;/code&gt; file named in the config, so adding or upgrading one is a config change: &lt;code&gt;plan&lt;/code&gt; shows it, &lt;code&gt;apply&lt;/code&gt; makes it live, &lt;code&gt;rollback&lt;/code&gt; takes it back. No rebuild, no restart. A plugin runs in a sandbox, with no files, sockets or processes unless the config grants them, so a broken one can&amp;rsquo;t take the server down. And a plugin can be written in anything that compiles to WebAssembly. Rust, Go, C++, Zig, AssemblyScript.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
