A friend of mine told me to get a .blog domain as reference to my name. So instead of Timlukas Bloch it would be timlukas.blog (I know it’s a bad pun).
I went forward and got the domain without any real use for it. It’s just another expensive domain to have laying around for the sake of being able to.
I don’t run a blog. I tried to, when I was younger, just for seeing how it would work. I didn’t come up with any content and deleted it again. Same plan was for this Medium page. I wanted to see how it works, especially how far the design options go, as I like the general look of Medium.
That in mind, I went and created this page. Nice. No content, but easy and good looking.
So I still had the timlukas.blog domain and now, in a way, had a blog. Obviously I wanted to use my .blog domain for my blog. But that’s where it was getting tricky:
As Medium uses HTTPS for every site, which is a good thing, they will need a valid TLS-certificate for every single one of them. And they will charge you a one-time fee of $75 for it.
So we do have Let’s Encrypt giving out free TLS-certs. Medium could use that. Some sites do that for their customers. Because it saves them actual money:
If you are using sub-domains, like Tumblr does, you could just get a wildcard certificate and be done. It’s a little costly, but worth it. By using complete custom domains, like Medium, you need a certificate for every site. That is expensive. Honestly a one-time fee of $75 is still ok, but over some years renewing all those certificates will cost Medium money, instead of earning them some by getting a little extra for the cert.
So using free certs from Let’s Encrypt would save money. But those certificates expire every three month and must even be implemented at first.
But, behold, there is a simple (and also free) solution: Caddy.
So what is Caddy? Its author describes it as “[…] the HTTP/2 web server with automatic HTTPS.” And that’s simply what it is. It’s written in Go, uses Let’s Encrypt, is Open Source, damn fast and also super easy and quick to set up. It does everything you’d expect from a modern webserver, but automatic.
And, of course, it solves the problem: Running the custom-URL blogs on Caddy would save Medium work and the users $75.
A nice example of that exact use-case are the public status pages from UptimeRobot:
Status Pages>Custom Domains are now HTTPs-enabled | Uptime Robot - Blog
However, this doesn't seem to work correctly. Over HTTPS, I receive the certificate for status.uptimerobot.com instead…
So as long as there is no similar feature on Medium I’ll just stick to my, not that fancy, 301-redirect. But I’d like Medium to implement such a feature. Of course it doesn’t have to be Caddy, but that’d be my suggestion ;)