Calculating primes is fairly straightforward so you calculate a few large prime numbers, and do some math to them.
Now you have a strong key that didn't require a supercomputer to create but taking that final number and turning it back into those original primes is a much more computationally expensive proposition.
In fact, it's one that's not viable with current technology.
I use a DNS server on my local network, and then I also use Tailscale.
I have my private DNS server configured in tailscale so whether on or off my local network everything uses my DNS server.
This way I don't have to change any DNS settings no matter where I am and all my domains work properly.
And my phone always has DNS adblocking even on cell data or public Wi-Fi
The other advantage is you can configure the reverse proxy of some services to only accept connections originating from your tailscale network to effectively make them only privately accessible or behave differently when accessed from specific devices
It was not managed, honestly I should've disabled bitlocker, I just never expected it to be a problem.
As to settings for when it installs updates, they didn't seem to stick or were not always respected in my experience. I spent a bit of effort trying to make sure it wasn't configured to do that but it would still just go for it anyway if the system ever became idle after midnight or so.
Anyway this story has a happy ending because after that I decided to give daily driving linux another shot, and none of the issues I had experienced previously still exist here. In fact, incredibly enough I have found on average that the games I play perform better on Linux now than they did on Windows. And my OS never installs updates without my permission, let alone forcing an unscheduled reboot.
No seriously though, I aliased the apt command to nala and I use it instead.
It works nicely with grc for colors in the console and more importantly it supports simultaneous downloads so it runs through a large queue of updates much more quickly.
Another cool trick is using tailscale to ensure your portable devices always can access your Pihole(s) from anywhere and then setting those server's tailscale addresses as your DNS servers in tailscale.
This way you can always use your DNS from anywhere, even on cell data or on public networks
I keep a third instance of Pihole running on a VPS and use it as the first DNS server in tailscale so it will resolve a bit faster than my local DNS servers when I'm away from home
Part of that I'm sure it's the fact that I work nights, but Windows refuses to acknowledge that during my work hours is not an appropriate time to install updates.
Simply stepping away to get a coffee or use the restroom is enough for Windows to decide now is the time to reboot and install updates for an hour or so and you better hope you saved everything before stepping away.
As a matter of fact, one of those instances is the one where the update broke my bitlocker encryption and I lost everything that wasn't backed up. That was my last day using Windows.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package friends
E: Unable to locate package to
E: Unable to locate package play
E: Unable to locate package games
E: Unable to locate package with
And as many others have mentioned, it can be self-hosted as well.
Also fun side note:
As long as you are logged into a GitHub account and in a desktop browser you can press the . key on your keyboard while viewing any GitHub repo to open it in vscode web.
Putting Cloudflare as my secondary would allow some requests to get through and then often the device whose requests went to Cloudflare would continue using Cloudflare for a while.
The best solution I found was to run a second Pihole and use it as the secondary.
You can use something like orbital sync to keep them syncronized
Try Matrix bridges or Beeper