Archival block-list / opt-out mechanisms
There are many reasons for which we would like to avoid archiving some origins, including:
- owner or administrator requests ("opt-out")
- technical reasons (e.g. known-bad repositories, such as large datasets, or VCSes used as databases)
- legal reasons
We should design, implement and deploy some centralized (blocklist) and decentralized (robots.txt-like) mechanisms to block some origins from being archived.