Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://fed.qaz.red/users/elithebearded/statuses/113760064940191261">Eli the Bearded (elithebearded@fed.qaz.red)'s status on Friday, 03-Jan-2025 13:54:23 JST</a><a href="https://fed.qaz.red/@elithebearded" title="elithebearded@fed.qaz.red"><img src="https://gnusocial.jp/avatar/38461-48-20221129232903.webp" width="48" height="48" alt="Eli the Bearded" style="position: absolute; left: 0; top: 0;">Eli the Bearded</a><div><ul><li><li><a href="https://gnusocial.jp/user/227885" title="jessienab@wetdry.world">Jessie Nabein :neofox_peek_owo:</a></li></ul></div></section><article><p><a href="https://wetdry.world/@jessienab">@jessienab</a> <a href="https://cathode.church/@rgb">@rgb</a> </p><p>I remember when JPEG was a new thing and people decompressing their GIF files to recompress as JPEG despite the two having very different lossiness patterns.</p><p>People are weird about image compression. Codinghorror has several posts about improving image compression but HTML and javascript size optimization is largely ignored. "What if Discourse didn't send two copies of every post on forum page loads? Nah, too complicated."</p><p><a href="https://blog.codinghorror.com/zopfli-optimization-literally-free-bandwidth/" rel="nofollow noreferrer">https://blog.codinghorror.com/zopfli-optimization-literally-free-bandwidth/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4304449#notice-8414548">In conversation</a><time datetime="2025-01-03T13:54:23+09:00" title="Friday, 03-Jan-2025 13:54:23 JST">about 6 months ago</time> <span>from <span><a href="https://fed.qaz.red/@elithebearded/113760064940191261" rel="external" title="Sent from fed.qaz.red via ActivityPub">fed.qaz.red</a></span></span><a href="https://fed.qaz.red/@elithebearded/113760064940191261">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: blog.codinghorror.com</div><h5><a href="https://blog.codinghorror.com/zopfli-optimization-literally-free-bandwidth/">Zopfli Optimization: Literally Free Bandwidth</a></h5><div></div></header><div>In 2007 I wrote about using PNGout to produce amazingly small PNG images
[https://blog.codinghorror.com/getting-the-most-out-of-png/]. I still refer to this topic
frequently, as seven years later, the average PNG I encounter on the Internet is
very unlikely to be optimized.For example, consider this recent Perry Bible</div><footer></footer></article></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Eli the Bearded (elithebearded@fed.qaz.red)'s status on Friday, 03-Jan-2025 13:54:23 JSTEli the Bearded
- notorious rgb
- Jessie Nabein :neofox_peek_owo:
@jessienab @rgb
I remember when JPEG was a new thing and people decompressing their GIF files to recompress as JPEG despite the two having very different lossiness patterns.
People are weird about image compression. Codinghorror has several posts about improving image compression but HTML and javascript size optimization is largely ignored. "What if Discourse didn't send two copies of every post on forum page loads? Nah, too complicated."
https://blog.codinghorror.com/zopfli-optimization-literally-free-bandwidth/
In conversationabout 6 months ago from fed.qaz.redpermalink
Attachments
1. Domain not in remote thumbnail source whitelist: blog.codinghorror.com
  Zopfli Optimization: Literally Free Bandwidth
  In 2007 I wrote about using PNGout to produce amazingly small PNG images [https://blog.codinghorror.com/getting-the-most-out-of-png/]. I still refer to this topic frequently, as seven years later, the average PNG I encounter on the Internet is very unlikely to be optimized. For example, consider this recent Perry Bible

Public

Embed Notice

HTML Code

Corresponding Notice