nextcloud / nextcloud/logreader
See what we can do about false positive in EasyList/EasyPrivacy ad blocker
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 69
- Forks
- 30
- Avg merge
- 10h 28m
- Merged PRs (30d)
- 57
Description
Can we fix that?
Originally posted by @Dennis1993 in https://github.com/nextcloud/logreader/issues/1134#issuecomment-1913312715
Looks like the rule that matches is this one:
Not sure there's much we can do about this, but worth looking into before we rule it out.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the false positive in logreader with the EasyPrivacy rule linked at easyprivacy_general.txt line 305, then compare the behavior with that rule disabled. Determine whether the issue can be addressed in logreader or must be reported to EasyList, and document the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100