<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Core on BareProxy.com</title>
    <link>https://bareproxy.com/tags/core/</link>
    <description>Recent content in Core on BareProxy.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 31 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://bareproxy.com/tags/core/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>BareProxy Adds a Drift Watcher for DNS Records and TLS Certificates</title>
      <link>https://bareproxy.com/bareproxy-adds-a-drift-watcher-for-dns-records-and-tls-certificates/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-adds-a-drift-watcher-for-dns-records-and-tls-certificates/</guid>
      <description>&lt;p&gt;BareProxy 0.16.0 adds a drift watcher. You give it a list of domains, a few or a few hundred, and it tells you when something about them changes or is about to break.&lt;/p&gt;&#xA;&lt;p&gt;Certificates are the classic case. Renewal fails quietly, and the first sign is a browser warning on the live site. DNS is the other one. A record edited by mistake, a registrar that moved your nameservers, a missing MX after a migration. None of it shows up until mail stops or a page goes dark.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BareProxy Adds a Webhook Inbox That Keeps Every Event Until the App Takes It</title>
      <link>https://bareproxy.com/bareproxy-adds-a-webhook-inbox-that-keeps-every-event-until-the-app-takes-it/</link>
      <pubDate>Sat, 31 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://bareproxy.com/bareproxy-adds-a-webhook-inbox-that-keeps-every-event-until-the-app-takes-it/</guid>
      <description>&lt;p&gt;BareProxy 0.16.0 is out with a webhook inbox. It takes webhooks from Stripe, GitHub, Shopify and anything else that sends them, writes each one to disk, and then hands it to your app. If the app is down, the inbox keeps trying until the app is back.&lt;/p&gt;&#xA;&lt;p&gt;Webhooks have a weak spot. The sender tries a few times and then gives up. An app that is being deployed, or has crashed, or is simply slow for ten minutes, loses whatever arrived in that window. Most teams find out when a customer asks why a paid invoice still shows as unpaid.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
