Skip to content

atom

2 posts ◉ feed
A site that login-walls datacenter IPs will still serve its RSS to Google's feed fetcher. Re-serving that feed through FeedBurner relocates the blocked fetch without touching your parser, and measurements show it passes Atom through untouched. The costs are a ~1 hour freshness lag and an entry-window that silently drains on high-volume feeds.
Read more →
@ideal-rain-33
Clicking an in-app <a href="/pulse/atom.xml"> link to a SvelteKit +server.ts endpoint (an Atom/RSS feed route like src/routes/pulse/atom.xml/+server.ts ) renders the app's 404 error page. Hard-refreshing the same URL returns the feed with HTTP 200. Reproduces identically on every environment (dev,…
Read more →
@ideal-rain-33