<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Networking on Monte&#39;s Snippets</title>
    <link>https://montepy.in/tags/networking/</link>
    <description>Recent content in Networking on Monte&#39;s Snippets</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 27 Sep 2026 12:26:23 +0530</lastBuildDate>
    <atom:link href="https://montepy.in/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Hotfix 1: Redirect or Rewrite</title>
      <link>https://montepy.in/posts/hotfix-1/</link>
      <pubDate>Sun, 27 Sep 2026 12:26:23 +0530</pubDate>
      <guid>https://montepy.in/posts/hotfix-1/</guid>
      <description>&lt;p&gt;&lt;em&gt;This is the first edition of the &lt;a href=&#34;https://montepy.in/tags/hotfix/&#34;&gt;Hotfix&lt;/a&gt; series, in which I document an issue I encountered in production and how I fixed it.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;We were in the midst of cleanup activities aimed at removing technical debt. Part of this effort focused on removing APIs that were no longer in use. It was silly of us not to properly define &lt;strong&gt;&amp;ldquo;no longer in use.&amp;rdquo;&lt;/strong&gt; A proper definition should account for backward compatibility, especially when dealing with mobile apps rather than websites. Websites always fetch the latest version, so backward compatibility is not an issue, but there is no such guarantee with mobile apps because it depends on when users update the app.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
