Page MenuHomeSoftware Heritage

support origin blacklist for archive search and browse
Open, HighPublic

Description

In the near future, we may be requested to dereference certain contents, like it happens on https://github.com/github/dmca, and we need to be prepared.

The first step is to implement a classic blacklist/whitelist functionality on the search engine we provide (currently, just on the origins).
It can be based on exact match, or on regex.

Event Timeline

zack renamed this task from Implement a blacklist/whitelist feature on the search engine of the archive to support origin blacklist for archive search and browse.Jun 13 2018, 12:12 PM
zack triaged this task as Low priority.
zack added a project: General.
olasd added a subscriber: olasd.Jun 13 2018, 1:44 PM

The simplest approximation of this that I can see is adding a visibility column to the origin table, and tweaking that manually when we get a request.

Seems a nice way to go: we would also need some easy to use interface to
edit the "visibility" bit too...

Roberto Di Cosmo


Computer Science Professor

(on leave at INRIA from IRIF/University Paris Diderot)

Software Heritage E-mail : roberto@dicosmo.org
INRIA Web : http://www.dicosmo.org
Bureau C123 Twitter : http://twitter.com/rdicosmo
2, Rue Simone Iff Tel : +33 1 80 49 44 42
CS 42112

75589 Paris Cedex 12

GPG fingerprint 2931 20CE 3A5A 5390 98EC 8BFC FCCA C3BE 39CB 12D3

rdicosmo raised the priority of this task from Low to High.Jul 2 2020, 8:21 PM

This is an important feature: it has been dormant for a while, but we need to actually start implementing it.