3 ms·
Yeah, not happy about that idiocy (probably 1MB as video) burning through 10% of my monthly bandwidth on the first day of the month...
by mynewtb 8y ago
Yeah, not happy about that idiocy (probably 1MB as video) burning through 10% of my monthly bandwidth on the first day of the month...
- jasonmp85 8y agoI think "1MB as video" actually _hugely_ overestimates the size that file could be if it were just e.g. mp4 with the same frame rate, quality, etc.
- CydeWeys 8y agoWow, how low is your monthly download cap?? What ISP and where?
- flukus 8y agoProbably mobile, here are the plans mine offers (I'm on the 2GB one): https://www.whistleout.com.au/MobilePhones/Carriers/iiNet https://www.whistleout.com.au/MobilePhones/Carriers/iiNet So page bloat is a real issue, not just "old man rants about good old days". A shame really because the rest of the page is pretty light wieght, 5.2kb for the content and 2.2 for the css. Even worse is that the static preview of the monster gif is the second largest element.
- baud147258 8y agoHey, I've got a 50 MB mobile cap myself. But I don't complain since it's a free add-on on my phone+text plan.
- lucb1e 8y agoI used to have 250MB free with my internet contract until the ISP silently upgraded it to 500MB recently (must have been the past year or so, not sure when). If you use it only occasionally to read a few articles, you can do fine with only a few megabytes. Heck, I'd almost say kilobytes if bloat wasn't so common. Anyway, that's until shit like this comes along. If you were truly trying to watch a video---sure, that uses a lot of that tiny data bundle in one go, but a gif that should have been a video truly leaves you wondering why was this necessary?!
- exikyut 8y agoYou just made me think of a GIF-to-mp4 conversion service that runs as a proxy. Sadly, because of the "HTTPS everywhere!!!11" thing, such a service would not be viable (it would need to rewrite the <img> to a <video> in order to work, of course).
- pjc50 8y agoOpera were offering something like this for a while. With the support of a browser and HTTP proxying it's not a problem, the SSL terminates at the proxy and is re-encrypted under the proxy's SSL. Many web services will take an uploaded gif and turn it to webm before showing it, e.g. Twitter.