Once the images are loaded it doesn't flicker, if you press the +1 button a few times it flickers but when you go back with -1 everything is already loaded and it doesn't flicker.
It makes so much sense it hurts, especially when we think of desktop links, home page pins, etc.
The whole "bundle multiple sizes of animated files into one container" is crazy when they are nearly always different resolutions of precisely the same file.
If we have SVG we could modify the SVG at runtime to have it display additional data really easily.
As for video in favicons... kill me now. SVGs and a strict limit on favicon sizes would be good (enforced by browsers, ditch anything over 50KB - it should be more than enough!).
A nice bug I saw recently was that a server could be instructed to send an infinitely sized favicon, and the browser would happily consume it. Nice way to drain a phone battery, use all of the connection bandwidth, and just to play havoc.
What I want from favicons:
1) SVG
2) SVG support for icons in all major OS's so that desktop links and homepage links just work as SVG
Do SVGs really perform better than pixel are for what favicons are used for? I was under the impression that vector graphics performs poorly at small sizes.
From a business's perspective, the MIT license is similar the BSD license: you can incorporate MIT licensed code into commercial products/proprietary code and only have to include copyright notices. GPL has source code disclosure implications which can be deal breakers for some businesses.
Making something dual licensed allows for the next dev to make modifications and then release those mods under his/her preferred license. You could make a mod of favicon.js and release your mod under GPL to ensure any further modification of your code and your favicon.js branch stays under GPL.
Didn't read the code of this specific project but if recall correctly, you can change the favicon by setting it in the dom to the base64 representation of the icon data any time. From there, generating animations is just a question of filling pixels data with the canvas API and getting the resulting base64 string out of said API as well. Obviously all of this works only if the browser is relatively modern.
There is not a single Favicon visible for me on this site. Guess they are all loaded remotely or something. No idea. Chrome / Ublock Origin / Privacy Badger.
Animated favicons are a huge distraction and suck. From the looks of it this project aims to make the favicon display useful information like notification counts instead of animated loops.
The webcam is a hilarious example. Reminds me of this 1-dimensional video game you can play in your address bar. http://glench.com/hash/