Fixing Google’s Feedburner problem, and caching that half works 0 ▲ Joshua Rogers’ Scribbles 4 hours ago · 8 min read1534 words · Tech · hide Getting around Feedburner In a previous post, I talked about how Google’s Chrome Releases blog was serving stale results on its Atom feed, and had set up a redirect from its RSS feed (which was serving up-to-date results) to … the stale Atom feed. This meant results were up to a few days old. This was particularly annoying because my CCBot parsed the blog’s feed to notify me (Opera!) about Chromium vulnerabilities which were fixed. When I wrote that post, the Atom feed was days behind: $ date Sun Feb 23 22:33:37 AEDT 2025 $ curl --silent "https://feeds.feedburner.com/GoogleChromeReleases" | grep -o '2025-02-..' | sort -n | head -n5 2025-02-16 2025-02-13 2025-02-13 2025-02-13 2025-02-13 And the RSS feed (which historically was serving fresh results) was redirecting to the Atom feed: $ hcurl 'https://www.blogger.com/feeds/8982037438137564684/posts/default' HTTP/2 302 location: http://feeds.feedburner.com/GoogleChromeReleases Well, lo and behold, a few days ago I came to discover that… Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town