// 20051207 temporary fix

Aaand it's submitted in voatdev!
/v/voatdev/comments/1314056

Thanks for your support!

Sorry to disappoint, but I'll be updating the image after I've improved the script.
I'll try so snapshot another post of yours ;-)

Indeed. However, I didn't like the parts where it installs additional packages without asking first, and then requires apache to be stopped before it can even show the --help switch. That was quite scary and obscure, to say the least. But it's alright now.

It's done!

I'm currently reading documentation on let's encrypt. In the process of installing it. I'll switch to HTTPS soon.

Cheers!

Exactly. 40% of the times, it's under example.com/favicon.ico, which can contain 16×16 + 32×32 + 64×64 + 128×128 versions of the icon, each in BW, 1bpc, 2bpc, 8 bits per color, with transparency, the other 60% I need to download another HTML document to find the <meta tag> containing the appropriate information.

I had to make it more official, so I just bought a new domain name.

Now I also need an SSL certificate for this domain to serve content over HTTPS.

Only then can every body use it safely. And I shall post in /v/voatdev/ (again)

Because we can?

More seriously, it's about doing this so we can also do this.

Example.

More info: http://favicon.netk6.com/
Improve voat: http://favicon.netk6.com/voat.html

Unfortunately, yes.

Some websites link the favicon from the HTML and use the largest icon they have, e.g:

<link rel="icon" href="touch-icon-ipad-retina.png">
<link rel="apple-touch-icon" sizes="152x152" href="touch-icon-ipad-retina.png">

If I don't find an exact 128×128 version of the favicon, I downsize the one that is just a bit larger.
Ultimately, I will downsize that 152×152 version if I don't find a 16×16 one.

On the other hand, some websites do it the right way, serving a <1KB favicon containing layers from 256×256 to 16×16, in 2, 4, or 8 bit per color version. Impressive.

I've updated the homepage. I find it looks nicer like that. Those numbers are better on the top.

Thanks for the feedback!

Just to let you know that I've looked in the case-sensitivity issue, but the fix won't be easy considered the current architecture and rewrite rules. I'll have more time over the week-end though.

Cheers!

Thanks for the useful link. I'm planning to find a way to display the best version depending on screen resolution and DPI. This will be useful!

Thank you a lot for this bug report, you are correct!

URL paths are case sensitive, but domain names aren't.

I'm looking into it right now. I'll report back!

It's fine! Unless you didn't even look at the page, it means I did not properly construct it.

Back to the blackboard!

There's a little table with this information on the homepage.

Here is it:

*edit: … aaand it's updating, numbers are increasing again!

Yeah, buddy! fuck facebook!

Not a all! Thanks for your interest.

It's a mixture of shell scripts, imagemagick, PHP and tweaked Apache configs on a crude Debian install. Nothing fancy on the software side. Hardware is much better.

There's no framework, as I wrote it all myself. The first update (connecting to +1 million websites) took about 8 hours. A refresh now takes about 2.

Cheers!