Re:Engineering for Slow Internet
by camel-cdr on Friday May 31, 2024 @02:43AM
(#40532125)
It's not only the services them self. I have a very slow mobile connection, and one thing that bothered me immensly is downloading images in the browser:
How is it, than when I go to a .jpg url to view an image in the browser it takes way longer and sometimes times out, than hopping over to termux and running wget.
I had this problem with both firefox and chrome based browsers.
Note that even the wget download usually takes 10-30 seconds on my mobile connection.
[ Parent
| on HN ]
I have the same issue with nearly every static asset.
Browsers usually try to multiplex things, sometimes even the same image if the server supports "get specific byte range" or whatever.
There may be a setting to turn a browser back into a dumb wget visual displayer.
Re:Engineering for Slow Internet
by armchair_expert on Friday May 31, 2024 @02:10PM
(#40538468)
You can try going into proxy settings and setting to "none" instead of autodetect. Also, the dns server used by the browser could be different (and slower).
Re:Engineering for Slow Internet
by giantrobot on Friday May 31, 2024 @04:50PM
(#40540091)
Too many services today do stupid image transcoding today. While the URL says jpg it will decide that because your browser supports WebP that what you really must have wanted was a WebP. It'll then either transcode or just send you WebP data for the image or send you a redirect. This is rarely what you actually want.
With wget it sends you the source you actually requested and doesn't try to get clever (stupid). Google likes WebP so that means everyone needs to join the WebP cargo cult even if it means transcoding a lossy format to another lossy format.