6 ms·

"""In our tests, uBlock is unable to block the port scans in the new Microsoft Edge or Google Chrome as the extension does not have adequate permissions to uncl

"""In our tests, uBlock is unable to block the port scans in the new Microsoft Edge or Google Chrome as the extension does not have adequate permissions to uncloak the DNS CNAME records.""" Seems highly relevant...

AdmiralAsshat 6y ago
All the more reason to stay with Firefox.
- garren 6y ago
  And/or NextDNS.io - Uncloaking cloaked domains is primary what brought me to the service. Added benefits include service across all browsers, all devices, local/mobile etc.
  - ray991 6y ago
    But that is just swapping one privacy issue with another, as NextDNS is also free to sell user’s private metadata to data brokers. https://news.ycombinator.com/item?id=23318830 https://news.ycombinator.com/item?id=23318830
- dhimes 6y ago
  One problem I seem to be having with FF (on Win 10 anyway) is it's not checking my hosts file for a domain lookup before using dns. Overriding the hosts file makes some things easier so I tend to do it. But now, my first time trying from Win, and it's not getting my page. Chrome works, ssh from WSL works, but FF uses dns first, apparently. It's the first development usage I've found that Chrome works better than FF.
  - airstrike 6y ago
    Well, that just means Firefox is winning this war by, what, 79–1 rather than 80-0
    - dhimes 6y ago
      Agree.
  - mrj 6y ago
    Yeah I had that problem too after they shipped encrypted dns. You can turn that off and it'll work normally.
    - dhimes 6y ago
      OK thank you!
  - deadbunny 6y ago
    Are you using (or have been subjected to) Firefox enabling DNS over http? IIRC it's auto enabled for users in the US.
  - jlgaddis 6y ago
    If you want to use DNS-over-HTTPS, you can add domain names to "network.trr.excluded-domains" in "about:config" (if, for example, you always use the .dev TLD for custom hostnames in your hosts file, you can simply exclude that domain name). If not, well, just disable DNS-over-HTTPS entirely. See https://wiki.mozilla.org/Trusted_Recursive_Resolver https://wiki.mozilla.org/Trusted_Recursive_Resolver for even more DoH-related settings you can tweak.
    - dhimes 6y ago
      Thank you- that's very helpful!
- ta17711771 6y ago
  Or Chromium variants, if security is important to you.
  - ta17711771 6y ago
    See: per site isolation, Firefox X11 exploit, etc
tedivm 6y ago
I remember when Chrome started making these permission changes and claimed that it wouldn't affect things like ublock, despite the ublock authors saying otherwise. Google is going out of its way to use the power it has as the dominant web browser to weaken ad blocking, and anyone who cares about a free web should run screaming away from Chrome based browsers.
- BiteCode_dev 6y ago
  Don't worry, in 15 years they will use all the money they gained doing this, and start acting well again. Better even. And everybody will forgive, and people will defend them on HN for being redeemed, and they will be alright. That's been the trend.
  - BLKNSLVR 6y ago
    Microsoft only seem to be acting well again because they're in the company of entities acting worse. Google will have to be specifically not leading the charge, which may well be the case in 15 years. Google will be hiding behind a shield of some other companies worse behaviour in order to seem to be behaving well. Windows is still going backwards in terms of hostility to users.
    - insulanus 6y ago
      > Windows is still going backwards in terms of hostility to users. Do you mean that Windows is becoming more user-hostile, or less?
      - BLKNSLVR 6y ago
        Hahaha, yes, my wording is ambiguous, but you can probably gather from the tone and content of the first sentence that I mean it's becoming more user-hostile.
    - cirno 6y ago
      Truly, I don't know how one can look at Windows 10 and think Microsoft has in any way improved: the entire OS spies on you at every corner now, bloatware automatically installs in the background, updates are installed without your consent, and more.
bzb3 6y ago
Interesting. Anybody knows if these changes to the blocking API affect brave? I think I remember they said they wouldn't include them, but I don't really trust them.

AdmiralAsshat 6y ago

All the more reason to stay with Firefox.

garren 6y ago
And/or NextDNS.io - Uncloaking cloaked domains is primary what brought me to the service. Added benefits include service across all browsers, all devices, local/mobile etc.
- ray991 6y ago
  But that is just swapping one privacy issue with another, as NextDNS is also free to sell user’s private metadata to data brokers. https://news.ycombinator.com/item?id=23318830 https://news.ycombinator.com/item?id=23318830
dhimes 6y ago
One problem I seem to be having with FF (on Win 10 anyway) is it's not checking my hosts file for a domain lookup before using dns. Overriding the hosts file makes some things easier so I tend to do it. But now, my first time trying from Win, and it's not getting my page. Chrome works, ssh from WSL works, but FF uses dns first, apparently. It's the first development usage I've found that Chrome works better than FF.
- airstrike 6y ago
  Well, that just means Firefox is winning this war by, what, 79–1 rather than 80-0
  - dhimes 6y ago
    Agree.
- mrj 6y ago
  Yeah I had that problem too after they shipped encrypted dns. You can turn that off and it'll work normally.
  - dhimes 6y ago
    OK thank you!
- deadbunny 6y ago
  Are you using (or have been subjected to) Firefox enabling DNS over http? IIRC it's auto enabled for users in the US.
- jlgaddis 6y ago
  If you want to use DNS-over-HTTPS, you can add domain names to "network.trr.excluded-domains" in "about:config" (if, for example, you always use the .dev TLD for custom hostnames in your hosts file, you can simply exclude that domain name). If not, well, just disable DNS-over-HTTPS entirely. See https://wiki.mozilla.org/Trusted_Recursive_Resolver https://wiki.mozilla.org/Trusted_Recursive_Resolver for even more DoH-related settings you can tweak.
  - dhimes 6y ago
    Thank you- that's very helpful!
ta17711771 6y ago
Or Chromium variants, if security is important to you.
- ta17711771 6y ago
  See: per site isolation, Firefox X11 exploit, etc

tedivm 6y ago

I remember when Chrome started making these permission changes and claimed that it wouldn't affect things like ublock, despite the ublock authors saying otherwise. Google is going out of its way to use the power it has as the dominant web browser to weaken ad blocking, and anyone who cares about a free web should run screaming away from Chrome based browsers.

BiteCode_dev 6y ago
Don't worry, in 15 years they will use all the money they gained doing this, and start acting well again. Better even. And everybody will forgive, and people will defend them on HN for being redeemed, and they will be alright. That's been the trend.
- BLKNSLVR 6y ago
  Microsoft only seem to be acting well again because they're in the company of entities acting worse. Google will have to be specifically not leading the charge, which may well be the case in 15 years. Google will be hiding behind a shield of some other companies worse behaviour in order to seem to be behaving well. Windows is still going backwards in terms of hostility to users.
  - insulanus 6y ago
    > Windows is still going backwards in terms of hostility to users. Do you mean that Windows is becoming more user-hostile, or less?
    - BLKNSLVR 6y ago
      Hahaha, yes, my wording is ambiguous, but you can probably gather from the tone and content of the first sentence that I mean it's becoming more user-hostile.
  - cirno 6y ago
    Truly, I don't know how one can look at Windows 10 and think Microsoft has in any way improved: the entire OS spies on you at every corner now, bloatware automatically installs in the background, updates are installed without your consent, and more.

bzb3 6y ago

Interesting. Anybody knows if these changes to the blocking API affect brave? I think I remember they said they wouldn't include them, but I don't really trust them.