Question regarding cryptojacking toggle

[devipasigner]

All recommended lists (and alternate) include the cryptojacking list in NextDNS's built in cryptojacking protection. (with additional false positives removed).

So my question is why advise people to enable it? One of the lists are not maintained often and hagezi has stripped some false positives out of it.

[yokoffing]

Just thinking out loud: NextDNS internalized many of their lists, which weakened the case for this. They probably still use those one or two lists, but we cannot confirm that.

If we assume they use the same two lists:

• We could view this as a defense-in-depth and keep it enabled.
• We could encounter false positives that NextDNS does not allowlist but other maintainers do, and recommend users disable Cryptojacking Protection (your point).

Questions: Should we leave it enabled in case someone doesn't use the recommended privacy blocklists? What about the user who utilizes different lists?

cc: @hagezi @iam-py-test @DandelionSprout thoughts?

[hagezi]

I have activated it and have had no problems so far. Unfortunately, you can not see what is behind this function, because the lists are internal and not public. Maybe @romaincointepas or @rs can give information about this?

[SpidaXS]

I have activated it and have had no problems so far. Unfortunately, you can not see what is behind this function, because the lists are internal and not public. Maybe @romaincointepas or @rs can give information about this?

I don't recommend you enable this, there are many more false positive

[norilana]

[iam-py-test]

This is a known issue with the NoCoin filterlist (which I guess they are using?): hoshsadiq/adblock-nocoin-list#452