** "When you read an article about a Chromium bug or issue, chances are, it's also a Brave bug and issue, as they have based their browser on Chromium" **
Question here is if this is what broke Tor .onion address lookups really. Brave trying to on the sly invisible to user lookup domain C-Names to block tracking / malicious same domain attempts with its own internal DNS server. Expecting they are doing this via DOH (encrypted).
Key words: using an embedded DNS resolver
All this wouldn't be necessary if people were forced to serve their content from the same domain. The very same, without subdomain even. A website should be text + some images and maybe a standard format video. No junky JS needed. No heavy overhead. Just deliver the binary common objects and we are done. Handlers on computer to run the video. The HTML + stylesheet is cake. Long perfected.
All this sh!t is chasing imaginary dragons. Creating mythology to further imaginary industries. Want industry and need for solutions, create the problems.
“In Brave 1.17, Brave Shields will now recursively check the canonical name records for any network request that isn’t otherwise blocked using an embedded DNS resolver. If the request has a CNAME record, and the same request under the canonical domain would be blocked, then the request is blocked. This solution is on by default, bringing enhanced privacy protections to millions of users.”