<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Plugins on VPNW.com</title>
    <link>https://vpnw.com/tags/plugins/</link>
    <description>Recent content in Plugins on VPNW.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/plugins/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VPN Works Rebuilt as One Core With Plugins: What Moved Where in 0.3.0</title>
      <link>https://vpnw.com/vpn-works-rebuilt-as-one-core-with-plugins-what-moved-where-in-0.3.0/</link>
      <pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/vpn-works-rebuilt-as-one-core-with-plugins-what-moved-where-in-0.3.0/</guid>
      <description>&lt;p&gt;&lt;strong&gt;VPN Works started as five separate engines that each worked and didn&amp;rsquo;t add up to one thing. Version 0.3.0 rebuilt it from scratch as one small core, vpnw, with plugins for everything else.&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;The five engines of September were the Agent, Scope, Lab, Ledger and Exit. Each had its own binary, its own command line and its own browser demo. Underneath, the Agent&amp;rsquo;s code was already shaped like a core: a broker that takes every connection, a policy, paths, and one event model that everything spoke. What was missing was a way for everything else to plug into it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
