Reply to thread

Message

<blockquote data-quote="ForgottenSeer 92963" data-source="post: 972957">Flags I have enabled:#enable-webrtc-hide-local-ips-with-mdns - enabled#disallow-doc-written-script-loads - enabled#block-insecure-private-network-requests -enabled#edge-msb-all-dse - disabled#edge-digsig-enabled-pdf - enabled#edge-automatic-https&nbsp; - enabled#strict-extension-isolation - enabled#strict-origin-isolation - enabled#heavy-ad-privacy-mitigations - enabledI am unsure about a few flags, maybe others can provide feedback (please post your comments):<ul>
<li data-xf-list-type="ul">The Block scripts loaded via document.write 
It as old as Methusalems beard and originally only intended as performance improvement, now it is classified as bad practice in website design, but why is this setting still available? 
 
</li>
<li data-xf-list-type="ul">Allow Microsoft Search with Bing for any default search engine 
I am wondering whether this &#039;corporate searches&#039; refers to the Edge business version. I have disabled this, just to be sure, to prevent all my DuckDuckGo search request being copied to Bing also. 
 
</li>
<li data-xf-list-type="ul">Enable Digital Signature for PDF 
Most PDF&#039;s are not signed, but i do want to block PDF&#039;s with an invalid signature pretending to be safe. Probably not a useful flag, but I thought that it could not hurt to enable it. 
 
</li>
<li data-xf-list-type="ul">Heavy ad privacy mitigations 
With so little information on this flag (heavy ad blocking becomes deterministic), I assume that this is related to the sensitivity analysis whether or not this mitigation kicks-in. I have enabled it for quite some time, but I can&#039;t remember blocking something. So either it works seamlessly behind the scenes or it is useless in practice with Edge anti-tracking and uBlockOrigin on board.</li>
</ul></blockquote>

[QUOTE="ForgottenSeer 92963, post: 972957"] Flags I have enabled: #enable-webrtc-hide-local-ips-with-mdns - enabled #disallow-doc-written-script-loads - enabled #block-insecure-private-network-requests -enabled #edge-msb-all-dse - disabled #edge-digsig-enabled-pdf - enabled #edge-automatic-https - enabled #strict-extension-isolation - enabled #strict-origin-isolation - enabled #heavy-ad-privacy-mitigations - enabled I am unsure about a few flags, maybe others can provide feedback (please post your comments): [LIST] [*]The Block scripts loaded via document.write It as old as Methusalems beard and originally only intended as performance improvement, now it is classified as bad practice in website design, but why is this setting still available? [*]Allow Microsoft Search with Bing for any default search engine I am wondering whether this 'corporate searches' refers to the Edge business version. I have disabled this, just to be sure, to prevent all my DuckDuckGo search request being copied to Bing also. [*]Enable Digital Signature for PDF Most PDF's are not signed, but i do want to block PDF's with an invalid signature pretending to be safe. Probably not a useful flag, but I thought that it could not hurt to enable it. [*]Heavy ad privacy mitigations With so little information on this flag (heavy ad blocking becomes deterministic), I assume that this is related to the sensitivity analysis whether or not this mitigation kicks-in. I have enabled it for quite some time, but I can't remember blocking something. So either it works seamlessly behind the scenes or it is useless in practice with Edge anti-tracking and uBlockOrigin on board. [/LIST] [/QUOTE]

Verification