<?xml version="1.0" encoding="utf-8"?>
<!-- Hand-maintained Atom feed for the Overspan blog. No build step, so every
     published post needs an <entry> added here by hand, alongside the post
     file, the blog index, and sitemap.xml. Bump the feed-level <updated> to
     the new post's date each time. Entries appear newest first.

     Entry template (copy, fill, keep the timezone offset):

     <entry>
       <title>POST TITLE</title>
       <link href="https://overspan.dev/blog/SLUG"/>
       <id>https://overspan.dev/blog/SLUG</id>
       <updated>YYYY-MM-DDT00:00:00+12:00</updated>
       <summary>ONE-LINE DESCRIPTION, same as the post's meta description.</summary>
     </entry>
-->
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Overspan blog</title>
  <subtitle>Practical notes on using the Overpass API well.</subtitle>
  <link href="https://overspan.dev/blog/feed.xml" rel="self"/>
  <link href="https://overspan.dev/blog/"/>
  <id>https://overspan.dev/blog/</id>
  <updated>2026-08-20T00:00:00+12:00</updated>
  <author><name>Overspan</name></author>
  <entry>
    <title>Overpass 429 errors &amp; rate limits in production</title>
    <link href="https://overspan.dev/blog/overpass-429-rate-limits"/>
    <id>https://overspan.dev/blog/overpass-429-rate-limits</id>
    <updated>2026-08-20T00:00:00+12:00</updated>
    <summary>What a 429 from the Overpass API means, how the public servers' rate limiting works, and how to build a client that stops hitting the limits.</summary>
  </entry>
</feed>
