5 ms·
There are a few broken images there; could those be fixed?
by LinguaBrowse 6y ago
There are a few broken images there; could those be fixed?
- Grustaf 6y agoMaybe someone can reverse engineer the webpage and fix them?
- nuller 6y agoI am an html expert. I can help!
- ldjb 6y agoThe animations use the WebP image format. They work for me in Google Chrome on Android, but some browsers may struggle to display them.
- RodgerTheGreat 6y agoParticularly in the context of low-resolution pixelated graphics using a limited color palette, WebP seems a strictly inferior choice to the universally-supported GIF.
- loloquwowndueo 6y agoBurn all gifs https://burnallgifs.org/archives/ https://burnallgifs.org/archives/
- RodgerTheGreat 6y agoIf I follow, you are suggesting that web users protest a format that has been in the public domain for 17 years by instead using a format which has existed for less than 3, and in the process render content inaccessible to anyone not using a bleeding-edge browser?
- loloquwowndueo 6y agoI suggest we burn all gifs. Whether that leads to what you said is for you and others to decide :)
- digitalsushi 6y agoI mean all the licensing and incompatibility questions aside, one very cool thing about these newer formats is they (intentionally? unintentionally?) reduce our carbon footprint a little bit, by trying to save delivery costs. It would be pretty neat if my mac could make a thumbnail of a webp on my desktop, though. I mean without installing software, overriding security policies, or turning it into a developer laptop.
- gmueckl 6y agoIs there a good data set on energy requirements for transmission versus compression/decompression of data? Is it really that much in favor of compressed data?
- RodgerTheGreat 6y agoAs a concrete comparison, I downloaded the first webp figure on the page, "soft-drop-animation. The webp is 63,250 bytes. I used imagemagick to convert this file into a gif, resulting in a 119,265 byte file. I then ran the result through gifsicle[0] with maximum compression (-O3) to losslessly optimize it, producing a gif that is 29,711 bytes; less than half of the size of the original webp. As I noted higher on the comment chain, this usage scenario is particularly favorable to the gif format, while webp might come out ahead for photographic sources. [0] https://www.lcdf.org/gifsicle/man.html https://www.lcdf.org/gifsicle/man.html
- dubcanada 6y agoWhat browser are you using? Most support animated WebP so you must be using something old?
- shakna 6y agoSafari on macOS doesn't support animated WebP [0] except for Big Sur and later, which is pretty recent. [0] https://caniuse.com/webp https://caniuse.com/webp
- jwandborg 6y agoAccording to that page, Safari for Mac OS is at least one step behind every major browser except IE. I think it's fair to ask whether the images are broken or the Safari release process is broken.
- smoldesu 6y agoThanks for sharing this website, it's insane how far behind the curve Safari is on... well, every technology.
- PurpleFoxy 6y agoI have asked a few times at work if we can drop safari support because it’s blocking so many new features. No luck so far.
- smoldesu 6y agoGood luck.
- deleted 6y ago[deleted]
- stevebox 6y agoI just changed the graphics from webp to gif which should address this problem!
- RodgerTheGreat 6y agoThank you!