<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Releases on unweb.org</title>
    <link>https://unweb.org/tags/releases/</link>
    <description>Recent content in Releases on unweb.org</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 04 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://unweb.org/tags/releases/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Unweb 0.4 Signs In to Paid Proxies and Stops a Mac Going Direct When One Fails</title>
      <link>https://unweb.org/unweb-0.4-signs-in-to-paid-proxies-and-stops-a-mac-going-direct-when-one-fails/</link>
      <pubDate>Wed, 04 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://unweb.org/unweb-0.4-signs-in-to-paid-proxies-and-stops-a-mac-going-direct-when-one-fails/</guid>
      <description>&lt;p&gt;Most people who give a stranger a location pay for the proxy, and paid proxies want a user name and password. Unweb 0.3 refused those. It had a worse problem on a Mac, too. When a stranger&amp;rsquo;s proxy went down, macOS quietly sent its requests direct, from your own address. That&amp;rsquo;s the one thing a location must never do, and the 0.3 notes said so in bold.&lt;/p&gt;&#xA;&lt;p&gt;Unweb 0.4 fixes both with one small piece: a relay of Unweb&amp;rsquo;s own. It sits between the stranger and your proxy, on your own computer. It signs in to the proxy for the stranger, with SOCKS5 user name and password or HTTP Basic, because no web engine here can sign in to a SOCKS5 proxy by itself.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
