Skip to content

Implement periodically checked assertions #44

@myrdd

Description

@myrdd

Maintaining the lists is hard work – we should find a solution there. Some kind of assertions per rule could help. An example could be:

„In order to maintain the ‚allow‘ rule some-blog.com -> youtube.com in list ‚allow_embedded‘, there must be at least one request from http://some-blog.com/some-blog-entry.html to *.youtube.com.“

That assertion could be checked automatically, and the rule could be removed if the assertion fails, e.g. if the site goes down permanently.

The implementation could look like this (json format):

{
  "entries": {
    "allow": [
      {
        "o": {"h": "*.heise.de"},
        "d": {"h": "*.ix.de"},
        "assertions": [
          {
            "site": "http://www.heise.de/",
            "minMatchedRequests": 5,
            "minMatchedImages": 5
          }
        ]
      }
    ]
  }
}

The discussion started at #41 (comment).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions