Twitter | Search | |
RealFaviconGenerator
Favicon Generator. For real.
865
Tweets
10
Following
793
Followers
Tweets
RealFaviconGenerator Apr 18
Replying to @furederiqoo
Auto fix! I love that stuff! πŸ˜„
Reply Retweet Like
RealFaviconGenerator Apr 16
Replying to @furederiqoo
Thanks! :) So the site does not work with AdBlock enabled? It's smarter than I thought it was :-D Seriously I can't reproduce the issue. I get the Gulp code with AdBlock enabled. Is it a behavior you get every time you try?
Reply Retweet Like
RealFaviconGenerator Apr 4
Replying to @EudesTwt
Thanks 😊
Reply Retweet Like
RealFaviconGenerator Apr 3
Replying to @spjpgrd
Reply Retweet Like
RealFaviconGenerator Mar 22
Replying to @WorldAliveTours
You're welcome! 😁
Reply Retweet Like
RealFaviconGenerator Mar 21
Replying to @Daniel_Tonon
Thank you! ☺️
Reply Retweet Like
RealFaviconGenerator Mar 18
Then it was probably the best decision for 😁
Reply Retweet Like
RealFaviconGenerator Mar 18
Dropping the .ico is very tempting. Yet Google relies on it: . As boring as it sounds, a desktop icon reboot is the next big evolution of RealFavicon. Woohoo! :)
Reply Retweet Like
RealFaviconGenerator Mar 11
Replying to @hvzh
I would say the next step is to not deal with HTML code and images directly, but embrace the tech/framework you already use, eg.
Reply Retweet Like
RealFaviconGenerator Feb 20
Replying to @elimoto
The first tweet about Webpack is nearly two years old, I guess we can wait a few more weeks 😁 Yet I'm looking forward to try it!
Reply Retweet Like
RealFaviconGenerator Feb 20
Replying to @elimoto
Absolutely! If you think the plug-in is ready, please mail me the instructions to use it (no need for the perfect copy; readable content will do). Then I will evaluate it and add the Webpack tab πŸ˜€
Reply Retweet Like
RealFaviconGenerator Feb 11
Replying to @isuriv
A 192x192 touch icon? Where is it documented? What about the 96x96 favicon? Which browser is supposed to use it?
Reply Retweet Like
RealFaviconGenerator Feb 11
Replying to @Multinewmedia
You're welcome! 😁
Reply Retweet Like
RealFaviconGenerator Feb 4
Hi guys, when requesting , there is "access-control-allow-origin: *" in the headers. But when accessing , access-control-allow-origin is absent. See for an example of what this generates.
Reply Retweet Like
RealFaviconGenerator Jan 31
Replying to @marlonbishop
You're welcome! A a French, I live by the Baguette 😁
Reply Retweet Like
RealFaviconGenerator Jan 30
Replying to @fvsch @WalterStephanie
As a developer, I definitely agree. Unused files and versioning discrepancies are poison for the mind. RealFavicon's answer to this is to plug into reliable build chains, eg. with . From your point of view, there are no icons, only a single high res logo.
Reply Retweet Like
RealFaviconGenerator Jan 30
Replying to @WalterStephanie
Thank you Stéphanie! 😁
Reply Retweet Like
RealFaviconGenerator Dec 17
Replying to @jessegilbride
That's right. Actually this part should be completely rewritten to fit the round icons introduced in Android Oreo.
Reply Retweet Like
RealFaviconGenerator Dec 17
Replying to @h3artbl33d
Oh, that's right. The service was designed with the following figures in mind: - Upload a 1GB image: your RealFaviconGenerator session is down. - Upload a 1TB image: RealFaviconGenerator is down. - Upload a 1PB image: the hosting provider is down. Scaling down might help :)
Reply Retweet Like
RealFaviconGenerator Dec 13
Replying to @inspireants
It's okay as it is, really. The only drawback: you will notice 404 errors in your logs since accessing this icon is a convention defined by Apple. You can certainly live with this 😁
Reply Retweet Like