News for hackers. Stuff that matters.
Re:SVG favicons have some cool benefits by chrismorgan on Wednesday July 07, 2021 @03:23PM (#27764831)
Your favicon.ico can be compressed further to a 171 byte PNG. I confess I find this 271-byte incantation compelling despite increasing each response by that much, since it’ll load faster in the first place and avoid the overhead of another request:

  <link rel=icon href=data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACAAAAAgCAMAAABEpIrGAAAAG1BMVEU5PT85PT///7X22GDtiUvVOkKxOF5qMk////9bF0DJAAAAAXRSTlMAQObYZgAAAD5JREFUeNq906UBwEAUwNBy95+4cOA+09OxWSKsCE2wAQKCRhrsiMrgQFQGJ6IyuBCVwQ1YG1+wTHgQdpbTC3XuCmFsTKU6AAAAAElFTkSuQmCC>
Re:SVG favicons have some cool benefits by soheil on Wednesday July 07, 2021 @06:04PM (#27766239)
There won't be any overhead once the file is cached. Your method requires the favicon to keep getting downloaded on every page load.
Re:SVG favicons have some cool benefits by tyingq on Thursday July 08, 2021 @12:21AM (#27768457)
Both Chrome and Firefox (maybe others) have a separate cache for favicons that acts differently than the regular browser cache. I don't know if it caches data uris but it does cache more aggressively. I know some places like Stackoverflow add a cache-busting parameter to favicon.ico to get past it.
Re:SVG favicons have some cool benefits by soheil on Thursday July 08, 2021 @12:01PM (#27773793)
How would a data uri exactly get cached? It’s served inline with every page request.
Re:SVG favicons have some cool benefits by tyingq on Thursday July 08, 2021 @04:34PM (#27777261)
I know it sounds funny, but they want a favicon cache for things like the bookmarks page and the default "blank" Chrome page, where there's no "page" present. So it's possible they extract the uri data into that cache.
Re:SVG favicons have some cool benefits by playpause on Wednesday July 07, 2021 @07:43PM (#27767024)
It will load faster but at the expense of other things that matter more. On every page load, too. I don’t think it matters if a favicon download takes one extra round trip on the first page load. In fact I would prefer the request for the favicon to be deferred till after all my content and other assets have loaded, which I would guess browsers do by default.