This would be a great addition to /e/OS for those of us that would appreciate not needing a connectivity check but would still like to have the option to turn it on. It would be nice to have it turned off by default. The more information leakage we can control the better. This also would be nice given the current fallback from /e/'s servers are Foogle’s which is verified on the "What is the current state of De- googlisation on /e/ ?" document. Note that it admits, “This is a temporary, not ideal, situation because this solution relies on the confidence users can have in our project and infrastructure.”
@Manoj do you know if such has been discussed or considered?
Looks like this could be done from an in home, self-hosted NextCloud, no? Add the PHP 204 file or Apache webserver config. (both ate present in self hosted NextCloud, correct? ie can create PHP files in server OS and/or Apache database)
Can the terminal commands to the phone be done via ADB without root?
“Then, in a root terminal on the phone I entered the following two commands, from pat_512 in the Fairphone Forum (see links below).”
settings put global captive_portal_http_url "http://198.51.100.24/204"
settings put global captive_portal_https_url "https://example.com/204.php"
This might be easy for you but average user… A bit overwhelming
Oh i did not mean every user should do this, just wanted to share knowledge ;). By the way i tested this in my custom build and it works ok (the php way). So what i think /e/ should do is fix this, and remove the Google link in the source. I also got annoyed about the private dns calling home thing which i reported a year ago!, and this is also easy fixable…
Do you know of a published list of hosts to manually block in NextDNS or do you just manually watch the logs?
I just went into the log and found ......dnsotls-ds.metric.gstatic.com getting through so I added metric.gstatic.com to the denylist. Now to see if all sub-domians are blocked as well. I do have a number of blocklists already enforcing…maybe I need to add more?
You sparked me to check this with this👇 so THANK YOU!
With NextDNS, connectivitycheck.android is blocked.
I have decided to trust NextDNS even if it is not open source. Before, I used Quad9. But in any way, one have to trust a DNS server, so why Quad9 should be more trustable that NextDNS ? So let’s go for NextDNS.
Any opinion ?
“Privacy Central”, which I believe will do much of this tracker filtering at the system level, can’t get here soon enough!
Please share what you find further . Does this make you think of changing DNS? And thank you for your help.
Edit: Only FOSS apps and a few from Aurora can be found on my phone. The host file blocking here is a very nice feature . More discussion on /e/'s app store that I am following even though I don’t use it.
The NextDNS privacy policy sound great! But unfortunately one must trust, so once again another subjective choice! Back to original thought
Going back to a flip phone looks more and more appealing .
Phones generate a certain pattern depending on the apps / os installed. In my case i have some very specific calls to domains because i own them :). I think i have to let go my desire to be anonymous all the time… It is just not possible. Next DNS promises to not log your queries that helps…
Nope. I dont know.
For Signal, I noticed notifications where not available as soon as I switched to NextDNS. After checking the log, I saw mtalk.google was very regularly blocked. A quick search in DuckGo made me find that this tracker was needed. Then I whitelist it and Signal notifications came back imediatly.
The fact that Signal need a Google tracker to work puzzle me a bit…