Useed it for several localhosed services, like LiteLLM, what not always provide favicon (e.g. in DB-less mode)

This is an excellent way of blocking that "dark pattern" where a site puts a red dot on the favicon to keep you coming back.

Works perfectly! Thank you, Saber!

super easy to use! my tabs look very nice now :D

update (to ff130) just in time, thanks. its a very usefull add-on for my work.
i have the same webapp on two diferent servers an it works perfect for me.
but.. i cant find a "buy-a-coffee-button"

I have many Google Documents pinned in my browser and all their icons are the same non-descript, beside saying it's a Google document. Since I've installed this add-on, I have a different favicon for each of the document I have pinned. Productivity: increased. Mission: accomplished.

Installed 5 minutes ago, couldn't be happier, easy to install, and fun. But also useful, I had two icons for new tabs that I visit daily for work, I was able to change Jetstream to a SOQL icon as I use it for Salesforce and I changed Trello to their own, obvious, Trello icon. Recently switched to firefox for primary work and these kinds of extensions are helping make the switch even better.

Very nice addon! Thanks a lot. I used it to change the favicons of my pinned Nextcloud taps. I downloaded the favicon.ico for nextcloud calendar from github - and used the following URL-pattern: https://nextcloud..../apps/calendar/* I just drag and dropped the downloaded *.ico file to the small window when asked. :-)

hi, thanks for making this extension. It did just what i wanted without the need to adding my own userchrome.css

Hi! Excuse me, I installed this extension but I didn't understand how to find the Url imput box in which you can customize the favicon, can you help me?

It does it's job very nicely except when I try to do wierd things like go to ip addressed sites. If I have locations like 192.168.1.10 and 192.168.1.11 but also define an icon for 192.168.1.1 the ..1.1 icon gets applied to all three sites. I suppose I could just name everything in the local dns (or hosts file) and use names instead but this limitation seems quirky. :-)

The solution I ended up using was to define full ip and port for all sites that stand a chance of colliding. For instance defineing 192.168.1.1:80 keeps it from fighting with 192.168.1.1*:* so I'm golden now that I understand the landscape of the quirks. :-) My guess is the software does a simple search for each expression across all the entries and goes with the first one it matches up with regardless of whether other elements are present in the address. :-)