News for hackers. Stuff that matters.
Re:How to waste bandwidth, battery power, and annoy sysadmins by EdwardDiego on Saturday June 29, 2024 @04:29AM (#40828696)
Why should you need to provision a CDN when If-Modified-Since / Etags exist?

I get that not every client is well behaved, but you'd hope that Firefox would be, given Mozilla's presence in web standards.

(Which, tbh makes me think this issue is the "on iOS" bit, given it's Firefox. I presume Apple still has their "only Safari's rendering engine" rule in place for... ...reasons)

Re:How to waste bandwidth, battery power, and annoy sysadmins by yosefk on Saturday June 29, 2024 @05:58AM (#40829071)
A CDN caches across users, lowers latency by having servers closer to the user, and lowers the bandwidth your server needs to handle. Cloudflare CDN has a free tier and I assume others do, too, so it's fairly easy to provision.
Re:How to waste bandwidth, battery power, and annoy sysadmins by mcculley on Saturday June 29, 2024 @06:22AM (#40829179)
Why would the issue be “on iOS”? The renderer has nothing to do with how pages are fetched.
Re:How to waste bandwidth, battery power, and annoy sysadmins by jampekka on Saturday June 29, 2024 @06:37AM (#40829238)
They probably have to write a totally different fetching logic for the Safari wrapper. If Apple wasn't as scummy as they are, they would have used the same logic as in other platforms where this problem doesn't seem to exist.
Re:How to waste bandwidth, battery power, and annoy sysadmins by EdwardDiego on Wednesday July 03, 2024 @06:26AM (#40864600)
Because Apple.