Keeping your Fedora installation up to date can become a problem if your ISP imposes a strict datacap or if you’re stuck with only an expensive mobile data connection. Here are a few tricks for lowering Fedora’s system update bandwidth requirement.
Feed readers can be quite wasteful when it comes to bandwidth. A good implementation of HTTP caching, compression, and feed deltas can save both power and bandwidth for users and servers alike. Here is my detailed list of best practices for Atom/RSS feed publishers and feed readers.
Feed subscriptions consume a lot of bandwidth. It can be reduced with compression and HTTP caching. However, whenever one new item is added, every feed reader will download the complete feed anew. Feed delta updates solves this by extending on HTTP cache revalidation so a server would only return new entries after the last fetch.
I keep finding myself explaining how the Vary HTTP response header works and what effects it has on reverse-proxies and caching. Let’s find out if I’ve gotten any good at explaining it!
I’ve mentioned my Cache-Control plugin for WordPress before in passing, but I’d now like to explain what it does in more detail.
Debian’s package repository is distributed among many mirror servers. Picking the best mirror server previously required you to manually test network speeds, find the shortest geographic and network topological distance from your client (your PC), check that it was kept up to date, and then to regularly repeat these tests to confirm your mirror of…