â›”

Deny list primitive

What is this

Meet the ecosystem-raised need for a denylist standard and turn-key support to enable services to deal with DMCA, abuse like phishing, and other takedown requests.

What we need to do

This requires golden path work across the stack:

  • ✅ finishing spec work on denylist format (IPIP-383)
  • ✅ upstreaming reference implementation, making it turn-key, to unblock ecosystem to start building lists in userland
    • porting nopfs plugin to boxo/kubo
    • minimal UX support in kubo that allows gateway operators to implement mechanism responsible for updating denylist in userland (details)
  • documentation – an artifact to be a go-to resource we can send to people interesting in content filtering

Why?

Related Items