Android 18: you can only connect to approved wifi networks and visit approved websites.
this post was submitted on 27 Aug 2026
25 points (96.3% liked)
Android
22048 readers
258 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: !android@lemdro.id
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 3 years ago
MODERATORS
...this is the way.... /s
Sounds like a way to stop DNS adblockers.
You're absolutely right: adblockers (even via pi-hole) will be ineffective.
Not mentioned in this article, but ECH lays the foundation for each application to decide if they trust the upstream DNS provider or not.
Normally, an app trusts all pre-installed CAs. If any of these CAs were to issue a fraudulent certificate, the app would be at risk from an on-path attacker. Some apps choose to limit the set of certificates they accept by either limiting the set of CAs they trust or by certificate pinning.
So using custom DNS to block/prevent unwanted updates and to block ads will be a thing of the past.
...but this does mean if your ISP or country is censoring the internet: their job has gotten much more difficult.
I disagree.
CA pinning has nothing to do with DNS.
CA pinning makes it harder to inspect the content of the connection e.g. via a Man-in-the-middle attack. But DNS-based blocking is not affected.
ECH has nothing to do with DNS.
DNS and DNS adblockers come before the ClientHello.
ECH is meant to make the wanted virtual host known without sending it as plaintext in the ClientHello.
Please refrain from commenting again.
If the article described it correctly this happens after DNS on the first connection to the target. So for users of PiHole etc. this won't change anything but - unless their service supports this - they won't benefit from it either.
Yeah, it's the next step of https in essence, unrelated to dns. Browsers have had it for about 2 years now. Of course websites also need to support it to get any benefit.
DNS is already "solved" via DOH, which for adblocking purposes you can disable or point to your own dns server.
ECH, this thing here, makes domain blocks impossible. Without it, advanced routers can use packet inspection to block connections to say example.org. With it, they would need to block IPs serving example.org, which would also block all other domains hosted frommthose IPs. Especially websites on big CDNs like cloudflare are essentially unblockable, you'd take down like 30% of the internet if you tried to block a single page on there.
Without ehc, traffic is indistinguishable between websites. With, it's indistinguishable between servers.