Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Web Extensions
uBlock Origin update thread
Message
<blockquote data-quote="ForgottenSeer 97327" data-source="post: 1027169"><p>It is true that static rules are a bit faster than dynamic rules and dynamic rules are a bit faster than cosmetic rules, but it would surprise me that you would notice it.</p><p></p><p>When you are the type of "set and forget" user, using dynamic rules for easy medium is probably the most convenient way to implement this. When you like to switch on hard mode on some websites to further strip them, it is easier to move the 'easy hard mode' or 'easy medium mode' blocking rules to the static rules section. In the picture below EDGE on STRICT seems to miss SEGMENT.COM (there is also a SEGMENT.IO). It is easy for me to block SEGMENT.COM with dynamic rules. I usually keep this dynamic rule for a few weeks and when it does not give me any problems I make it a static rule (1) when I encounter SEGMENT.COM on another website, I experiment with it for a while (does not break website functionality) and add it to my first static rule (2). When I encounter it on a third, I usually make it a generic rule (3)</p><p></p><p>1 dynamic rule: CNN.COM SEGMENT.COM * BLOCK translates to static rule: ||$*third-party,from=CNN.COM,to=SEGMENT.COM</p><p>2.dynamic rule: DOMAIN2.CO.UK SEGMENT.COM * BLOCK translates to static rule: ||$*third-party,from=DOMAIN2.CO.UK,to=SEGMENT.COM</p><p>3.dynamic rule: * SEGMENT.COM * BLOCK translates to static rule: ||SEGMENT.COM$third-party</p><p></p><p>[SPOILER="Using dynamci rules to weed out missed 3p"]</p><p>[ATTACH=full]273312[/ATTACH]</p><p>[/SPOILER]</p></blockquote><p></p>
[QUOTE="ForgottenSeer 97327, post: 1027169"] It is true that static rules are a bit faster than dynamic rules and dynamic rules are a bit faster than cosmetic rules, but it would surprise me that you would notice it. When you are the type of "set and forget" user, using dynamic rules for easy medium is probably the most convenient way to implement this. When you like to switch on hard mode on some websites to further strip them, it is easier to move the 'easy hard mode' or 'easy medium mode' blocking rules to the static rules section. In the picture below EDGE on STRICT seems to miss SEGMENT.COM (there is also a SEGMENT.IO). It is easy for me to block SEGMENT.COM with dynamic rules. I usually keep this dynamic rule for a few weeks and when it does not give me any problems I make it a static rule (1) when I encounter SEGMENT.COM on another website, I experiment with it for a while (does not break website functionality) and add it to my first static rule (2). When I encounter it on a third, I usually make it a generic rule (3) 1 dynamic rule: CNN.COM SEGMENT.COM * BLOCK translates to static rule: ||$*third-party,from=CNN.COM,to=SEGMENT.COM 2.dynamic rule: DOMAIN2.CO.UK SEGMENT.COM * BLOCK translates to static rule: ||$*third-party,from=DOMAIN2.CO.UK,to=SEGMENT.COM 3.dynamic rule: * SEGMENT.COM * BLOCK translates to static rule: ||SEGMENT.COM$third-party [SPOILER="Using dynamci rules to weed out missed 3p"] [ATTACH type="full"]273312[/ATTACH] [/SPOILER] [/QUOTE]
Insert quotes…
Verification
Post reply
Top