<story><title>PiVPN v4.6.0: The End</title><url>https://github.com/pivpn/pivpn/releases/tag/v4.6.0</url></story><parent_chain></parent_chain><comment><author>solarkraft</author><text>&amp;gt; &amp;quot;But I want and can maintain it, can I take it over?&amp;quot; Let me put it plain and simple: No! I don&amp;#x27;t know you, I don&amp;#x27;t trust you! Fork it and carry on!&lt;p&gt;They learned a good lesson from the liblzma situation.</text></comment>
<story><title>PiVPN v4.6.0: The End</title><url>https://github.com/pivpn/pivpn/releases/tag/v4.6.0</url></story><parent_chain></parent_chain><comment><author>nickjj</author><text>This really goes to show you how valuable a good experience &amp;#x2F; API is.&lt;p&gt;PiVPN is so easy to use. You run 1 command and pass in the name of the config to generate and you&amp;#x27;re done. Now you can take that config and use it client side.&lt;p&gt;I&amp;#x27;ve used it on Debian servers (not a Raspberry Pi) and it&amp;#x27;s been flawless to onboard a bunch of folks into using a VPN (work related).&lt;p&gt;IMO there&amp;#x27;s no way this project will fail, someone will fork it.</text></comment>