i messed with eos, it's alright. I had some problems with the mirrors breaking, to which the solution to fixing the broken keyring trust was "untrust the key, and forcibly install it" which i didn't really like. Other than that it seemed ok.
Run the eos updater tool and it takes care of all of that for you. The broken mirrors isnt an actual issue either since there's redundant mirrors on the mirror list I believe
oh believe me i did, it was fucked. The problem was that the keyring for EOS was out of date, and since i hadn't updated in long enough, there was literally zero chain of trust for that keyring to be updated somehow. So i had to forcibly update it.
I tried a variety of things, including updating eos mirrors iirc, nothing worked until i fixed the keyring lol.
How did you build this list? This is likely to break other things. Azureedge isn't just for ads, and msftconnecttest is literally only used to detect if your internet connection is working.
what? shouldn't blocked domains be routed to 0.0.0.0 instead of loopback? This might cause the system generally to wait for a response instead of instantly realizing those domains don't exists