Gateway ACL? about ipfs HOT 1 CLOSED

Maybe best to move this to the FAQ: https://github.com/ipfs/faq

I'll answer it here though as i'm currently offline.

Apologies if this is the wrong place, but is there any plans to implement
an ACL on the HTTP gateway to define which data is allowed to be pulled via
that gateway? (I.e has to have originated from your own nodes or some-such)

You can do this now already with the same ACLs that are on the API server.
Later on we'll have denylists and allowlists for more dynamic control. And
the best case will be the capability/token based auth planned for go-ipfs.
this last one is a few months out though.

In an Ideal world it wouldn't be an issue but we don't live in an ideal
world and thus some nodes have bandwidth restrictions or are in
jurisdictions where law enforcement is likely to be less than understanding
about what IPFS actually is.

Indeed. see also: ipfs-inactive/faq#47

from ipfs.