On Fri, Nov 8, 2019 at 4:20 AM Magnus Hagander <magnus@hagander.net> wrote:
> Applied and pushed, will take a while before it updates in all the caches.
I think that the new favicon looks weird when actually seen in the
browser. Not sure if that’s due to the fact that the anti-aliasing
needs to work differently for the larger variant (i.e. needs to scale
down because it’ll appear on a “retina” display), or if the logo is
inherently a bad target to use directly as a favicon due to the level
of detail. I think that it's probably the former, though, since there
are examples of this working better with logos that are of similar
complexity to our own.
The favicon has certain artifacts…the pixels don’t get smushed
together enough. I am not an expert, but I think that this could be
improved on.
--
Peter Geoghegan