Have you considered using a static site generator like Hugo/Jekyll/Gatsby? You could then host it using Github Pages for free. You automatically get a free SSL cert via Let's Encrypt and can use your own domain. You would only pay for your domain annually. Very fast, secure, and affordable.
Yes I was thinking of this indeed. I like it because of the zero-hackability. Though it will not allow me to accept comments and I want to avoid platforms like Disqus.
However I have zero discoverability that way, like I said in the post. I can write nice articles but nobody will come across them, even people that would have been interested. I'm not vain or anything if I say so myself but if I put in the work it would be nice if someone would actually benefit from it :)
This is the nice thing about platforms like Medium but they're all so commercial... I don't like that part. And I don't want to constantly market my blog everywhere. I just want it in a place where people could pick up on it if they find it interesting, and ideally where I could find such posts from others. A bit like Hacker News but then more for blogs itself.
It absolutely does not need to monetise in any way. I have a job :)
You get out what you put in when running a blog. You need to market your site unfortunately. That’s where SEO, social sharing, newsletters and all those other annoying things come in. Even on a platform with an existing audience, like Medium, you will still be drowned out in the noise, unless you’re *very* lucky.
Bonus to hosting your own stuff is that you own it and no one can take that from you.
I use PiHole with a DoH upstream. I want all devices on my network to use my DNS server. Mozilla's implementation is easily managed using their canary domain "use-application-dns.net" but Google doesn't have this option. I do not want any queries sent to Google. It is not feasible to manage chrome flags on every device, especially mobiles. Does anyone know if Chrome will be using their two public IP's, 8.8.8.8 and 8.8.4.4 for this new DoH service? If that is the case this will be easy to block at the network level. Thanks.
Chrome Enterprise (which, contrary to what the name might suggest, is not a paid enterprise offering) offers management tooling for managing flags across many devices. Here's the flag for DoH: https://cloud.google.com/docs/chrome-enterprise/policies/?po...
but Chrome Enterprise means it has to connect and phone home to Google all the time anyway, no? That defeats any potential benefit of having more control over the browser.
Given this is a "free" offering, the data being mined finances this service.
If parent wants to manage Chrome configuration across N devices, Chrome Enterprise is a good tool for the job. They may or may not care if their data is on Google servers or not. They might consider these two items to be two entirely distinct and different benefits.
If parent wants to avoid having any of their data cross Google machines, you are completely correct that Chrome is the wrong tool for the job.
Have you considered just blocking outgoing on port 53 on your network?
There are a few too many devices out there that have hardcoded DNS and don't respect the resolver communicated to it. (Chromecast is an easy example.)
Yes, 53 is allowed only to pihole and dropped everywhere else. I just blocked 853 on each pfsense interface. I will see how it acts when I get off work.
