-
This would mark as invalid all filters requiring a trusted source. The workaround to make My filters a trusted source would be to enable The reason is that I worry about users carelessly copy-pasting filters from random sources. Thoughts? |
Beta Was this translation helpful? Give feedback.
Replies: 14 comments 82 replies
-
I agree, too many user are copying & pasting rules from obvously untrustful sources now for yt. OTOH this will make debugging filter issues a bit harder when trusted filters are involved as we have to ask him to enable |
Beta Was this translation helpful? Give feedback.
-
Generic procedural filters still are behind a pref, so why not? |
Beta Was this translation helpful? Give feedback.
-
I think this is reasonable change. If it causes too much confusion, it can be reverted later (though it's probably fine). Btw, now as we are speaking about trusted sources, can we also get an advanced option that allows to mark specific lists as trusted? (Something similar like |
Beta Was this translation helpful? Give feedback.
-
Gave more thoughts to this, taking into account the other requests re. trusted scriptlets. This will not be controlled by
This way, one can also decide to trust lists maintained elsewhere. For example, for stock AdGuard lists add The token to use are the ones used in assets.json. You fully trust maintainer of List-KR? Add The matching is made with So this also opens the door to trust imported lists, for example: add |
Beta Was this translation helpful? Give feedback.
-
Considering what people are sharing are filters they're asked to test by a maintainer (which will be outdated by the time it is shared), and the fact that people tend to share these for self-satisfaction (internet points), what's stopping them from sharing the entire testing step shared by a maintainer in the future? I think this is a good change and obviously I don't have any suggestion, but I think I ought to make sure the maintainers know the problem from this angle. |
Beta Was this translation helpful? Give feedback.
-
Does this make debugging more difficult when filter maintainer requests user to test some filters? How it's now handled with scriptlets logging available in dev version only? |
Beta Was this translation helpful? Give feedback.
-
Could you also make it less restrictive by targeting domains instead of sub-domains for adding imported lists as trusted sources ? Example - |
Beta Was this translation helpful? Give feedback.
-
I want to add a warning sentence at the top of My filters, following the one already in there, but I am not confident enough about my English being correct. So I am thinking of: Do not add filters from untrusted sources. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
Yes, a color might be too distracting in the long run. Plus, it's difficult to choose a color for both themes (brown?). In any case, some kind of distinction would be better. At the very least |
Beta Was this translation helpful? Give feedback.
-
I at least give my approval to the Advanced Settings option. After all, there's more than a few scriptlets I want to (or sometimes have to) learn by trial and error, a fair few of which are considered trusted. |
Beta Was this translation helpful? Give feedback.
-
Trusted filters should be marked somehow in editor. |
Beta Was this translation helpful? Give feedback.
-
BTW shouldn't the checkbox sync with |
Beta Was this translation helpful? Give feedback.
-
So for one to actually add trusted filters from AdGuard, for example: Tracking Protection filter Have to import Just adding |
Beta Was this translation helpful? Give feedback.
Yes.