Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

We analyzed 425k favicons

iconmap.io

Post reply on HN
Print view View original

111–120 of 131 posts

Re: We analyzed 425k favicons

#111

Post by sokoloff »

ryan29 wrote: post #17

> In fact, I recommend that browsers ignore these hints because they are wrong much of the time. I don't agree. That's the kind of coddling that encourages incompetence. Instead of compensating for others' mistakes, just let their stuff break. I wonder if Safai on iOS ignores the hints. When I tested, I was surprised to see that pressing the share icon, which holds the option for `Add to Home Screen`, would cause a d…

I don’t see Postel’s Law cited here yet, which I find pragmatic and worth sharing/considering as I used to be in the “let their stuff break” camp.

https://en.m.wikipedia.org/wiki/Robustness_principle (Quite short)

Re: We analyzed 425k favicons

#112

Post by account42 »

jamesfinlayson wrote: post #69
nerfhammer wrote: post #35

Earlier quoted context omitted.

there are png optimizer programs, e.g. optipng

I found https://pngquant.org/ to be pretty good.

Note that unlike some of the other tools mentioned here, pngquant does lossy compression. Might still be the right tool in many cases, but it means you should check the output while e.g. optipng is a no-brainer to add to whatever your publishing pipeline is.

Re: We analyzed 425k favicons

#113

Post by mkotowski »

vbezhenar wrote: post #97
jiggunjer wrote: post #71

Earlier quoted context omitted.

wouldn't that preclude a few popular features like a rich text editor?

I thought about "serverless" blog. Here's some rough scheme I came up with (I never implemented it, though): 1. Use github pages to serve content. 2. Use github login to authenticate using just JS. 3. Use JS to implement rich text editor and other edit features. 4. When you're done with editing, your browser creates a commit and pushes it using GitHub API. 5. GitHub rebuilds your website and few seconds later your we…

So, essentially a site generated with Jekyll, hosted on GitHub Pages with Utterances [0] for comments and updated with GitHub Actions.

I don’t know if https://github.dev version of Visual Studio Code supports extensions/plugins, but if so, then there is also a rich text editor for markdown ready.

All that’s left would be an instant refresh for editing.

[0]: https://utteranc.es

Re: We analyzed 425k favicons

#114

Post by account42 »

vbezhenar wrote: post #99
scrollaway wrote: post #82

Earlier quoted context omitted.

You might be overthinking this. I agree with the philosophy that stricter is better, but in this case what do you expect broken hints to do? They’re not used for rendering, they’re used for figuring out what to fetch. A HEAD request would be far less efficient than knowing ahead of time what to fetch: 1 request versus 2N+1 requests. What you suggest sounds all fine but the entire web is user input for a browser, so n…

Just don't ignore filename extension. favicon.svg is SVG and that's about it. If you don't support SVG, don't download it. If you want to store png in favicon.svg, don't do that.

The web runs on mime types and file extensions are irrelevant except for buggy browsers that try to be too clever (Internet Explorer).

Re: We analyzed 425k favicons

#115

Post by account42 »

deathanatos wrote: post #95
mixmastamyk wrote: post #93

Earlier quoted context omitted.

Will it look good on a browser tab? Seems like the res would be too low.

It's a vector graphic; its resolution is whatever you render it at. "S" as in, "Scalable". Sure, there is some nuance in that you wouldn't want some fine detail to get lost at the displayed size, but presumably you know you're making a favicon when you do so. Or, you're the NFL & you're going to supply a 4 megapixel image IDK.

> Sure, there is some nuance in that you wouldn't want some fine detail to get lost at the displayed size, but presumably you know you're making a favicon when you do so.

On the other hand, SVG is really not designed for the fine pixel control you want to make the icon look good at smaller sizes as it does not have the equivalent of font hinting.

Re: We analyzed 425k favicons

#117

Post by fho »

That "I am feeling lucky" button does not seem random at all, it brought me in order to: Microsoft Windows, Blogger, The Financial Times, Github, Adobe ...

As every other location I randomly scroll to has no recognizable image on it ... that seems preselected :-)

Re: We analyzed 425k favicons

#118

Post by pixl97 »

shuntress wrote: post #54
jacurtis wrote: post #40

Earlier quoted context omitted.

What most of them do is they will use Wordpress exploits to get into random wordpress website ran by people who know nothing about managing a website and are running on a $3/mo shared hosting account. After they get into these random wordpress sites, then then embed links back to their sketchy site in obscure places on the wordpress site that they hacked, so that owners of the site don't notice, but search bots do. T…

> "had their nephew throw up a wordpress site instead of hiring a professional" The web is supposed to be accessible to everyone. This type of "blame the victim" attitude is a poor way to handle criminal activity.

There are plenty of places that you can go to on this planet with little to no law enforcement. Don't be surprised if you end up dead there. Handling global crime is very difficult.

Re: We analyzed 425k favicons

#119

Post by mrkramer »

1cvmask wrote: post #49

The favicon visualization brought memories of the million dollar homepage. I suppose it was precursor of NFTs. https://en.wikipedia.org/wiki/The_Million_Dollar_Homepage http://www.milliondollarhomepage.com/

>The favicon visualization brought memories of the million dollar homepage. I suppose it was precursor of NFTs.

It was not; NFTs are digital certificates saying that you own certain digital content on the other hand The Million Dollar Homepage was basically selling ad space on the website.

You can argue you could buy part of the website(digital space) and therefore you own the part of the website but in reality you were renting it as an ad space meant to promote your website(link).

Purpose and vision of The Million Dollar Homepage and NFTs are completely different but I can see similarities between quasi owning digital space(part of website) and owning digital content or digital certificate(digital token).

Re: We analyzed 425k favicons

#120

Post by pc86 »

vbezhenar wrote: post #97
jiggunjer wrote: post #71

Earlier quoted context omitted.

wouldn't that preclude a few popular features like a rich text editor?

I thought about "serverless" blog. Here's some rough scheme I came up with (I never implemented it, though): 1. Use github pages to serve content. 2. Use github login to authenticate using just JS. 3. Use JS to implement rich text editor and other edit features. 4. When you're done with editing, your browser creates a commit and pushes it using GitHub API. 5. GitHub rebuilds your website and few seconds later your we…

If this is a serious suggestion (I really hope it isn't), you have never met the kind of person setting up the blogs the GP is talking about.
Post reply on HN