18 comments

2

Why?

1

Because we can?

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

Example.

1

Oh, OK - thanks.

I take it grabbing/linking to the favicon from each site when generating the page would be slow and horrible or something?

1

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.

1

Blech. I can see why you're doing it now!

1

Hey, my post is in there! It's my lucky day!

1

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 ;-)

1

I support the improve voat!

maybe post this to /v/voatdev/ ?

0

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)

1

Just use certbot to enable lets encrypt. An easy way to acquire https

0

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

Cheers!

0

It's done!

1

Nice!

I did install let's encrypt on my own homeserver, so I can use owncloud with https, it is rather easy, with certbot handling the auto renewal.

0

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.

1

Ahh that is quite strange indeed. I am glad you got it anyway.

Cheers

0

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

Thanks for your support!

1

Nice, any day mate. I see you used Let's Encrypt for the SSL.

0