4 ms·
“This insanely unnecessary bandwidth usage penalizes sites that have long (>10) feeds with complete posts.” Since rss is text only the sizes are very small and
by prepend 8y ago
“This insanely unnecessary bandwidth usage penalizes sites that have long (>10) feeds with complete posts.”
Since rss is text only the sizes are very small and compress well. Considering the average web page is 3M[0], pulling down 10-100k of every post ever doesn’t matter. And http takes care of not pulling the same file over and over.
It’s certainly a downside, but completely useable as is, and better than any viable alternative.
As far as standards go, I prefer simple, static file, over something requiring dynamic response.
There’s also nothing stopping the site from limiting the RSS feed to only 5 posts with a link for full.
[0] https://speedcurve.com/blog/web-performance-page-bloat/ https://speedcurve.com/blog/web-performance-page-bloat/
- viraptor 8y agoEven better: instead of serving the generated for, point your RSS subdomain to your favourite CDN and only update your files when the site changes. That's likely to save you some money.
- jessriedel 8y ago> Since rss is text only the sizes are very small and compress well. Considering the average web page is 3M[0], pulling down 10-100k of every post ever doesn’t matter. My web pages are 100k and my RSS feed is 500k. > It’s certainly a downside, but completely useable as is, and better than any viable alternative. It doesn't fulfill the need I originally mentioned: making blog archives readable offline. > As far as standards go, I prefer simple, static file, over something requiring dynamic response. I agree static is better, but a dynamic response isn't necessary. You could just have a static file that listed all the blog posts, with a link to another static file for each post. This avoids having the user download 10 blog posts each time they want to poll if something new has happened.