It can be the same document but I think it would be clarifying for there to be a clear delimiter between the specification of how the content of the denylist is constructed and what the purpose of a content-decider and its interface is.
I believe this to be the case as there is already ways to implement content blocking on a CID basis, but currently there is no shared format in which to share the list of CIDs. It may take sometime for an actual content-decider to be implemented, and so that shouldn’t block the usefulness of sharing the denylist.
It can be the same document but I think it would be clarifying for there to be a clear delimiter between the specification of how the content of the
denylistis constructed and what the purpose of acontent-deciderand its interface is.I believe this to be the case as there is already ways to implement content blocking on a CID basis, but currently there is no shared format in which to share the list of CIDs. It may take sometime for an actual
content-deciderto be implemented, and so that shouldn’t block the usefulness of sharing thedenylist.