Yes, thanks for that suggestion, we all need reminders to follow the law sometimes.
Let's assume I am not breaking the law, and I want to be least responsible for others doing questionable things whilst using my gateway. Are there suggested configurations or guides for those that want to help the IPFS community by running a public gateway? Is there value in me providing such a service (with aims of stability and longevity) to the community? Or am I just wasting my time and resources? At the very least, I can use it for my personal/family uses, but I would like it to be safe also.
For now, I am considering:
Allowing writability (for POST requests)
Rate limiting at 10 GET requests per hour (this will change later)
Reducing total cache size to 2GB (if I see value, I may scale this up into the TBs, who knows)
My http frontend will close the connection after serving a file larger than 1GB (I would prefer if my ipfs daemon had the option to refuse to serve files larger than X)
These considerations are only to mitigate rampant warez (as well as other unmentionable illegal numbers) distribution coming from my gateway, as to reduce negative attention from authorities et al.
I understand it's impossible to prevent all/any illegal numbers from landing on IPFS, but I would still welcome some input, suggestions, or shared experiences about mitigating those sort of unwanted attentions, especially when you are specifically trying to prevent such uses on your gateway.
Any better suggestions other than "don't do illegal things!"? Or should I find a better place to discuss my concerns?