[Bug] Home page only shows the main domain's favicon about src.next HOT 5 CLOSED

@KaKi87
I investigated a little bit and found out that the original project besticons handle the subdomains too while logos.kiwibrowser doesn't, so seems like to be a server side bug i think
Comparing the example

Server	google.com	translate.google.com
Besticons	Link	Link
Logos.Kiwibrowser	Link	Link

@kiwibrowser you might take a look at that server

from src.next.

Potentially related to #158 (comment)

from src.next.

This , logically it's not a bug , the favicon is auto fetched by a server, it take the favicon from the website and in this case the website ( translate.google.com ) it's a subdomain of google.com so , it takes the favicon from last one .

Since that issue it's old and the default homepage will not undergo changes and implementation of new features, over time was born an alternative more customizable NextNTP which includes among other things the adding of custom logo on tiles

from src.next.

@d3ward This issue should then be transferred to https://github.com/d3ward/nextntp since this project uses the same favicon provider as the current NTP.

I see this as a bug because it does not seem logical to use the root domain's favicon when looking up a subdomain's favicon.

Google's favicon provider, for example, returns the subdomain's favicon : https://www.google.com/s2/favicons?domain=translate.google.com

from src.next.

With the new logos workflow , this issue is fixed

from src.next.