Block search engines with robots.txt to make it more difficult to for public instances to be abused #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now it's pretty easy to use Google/Bing/DuckDuckGo to find public unsecured Send instances.
This is a security hazard to the server owners, as I'm sure you know the original Mozilla was shut down due to malicious users using it to host malware/CSAM.
I propose limiting search engine access to make it harder to discover these instances, as this will greatly limit the abuse/DMCA violations that public hosters have to deal with.
Advanced users wanting to allow search engine indexing will no doubt be running a reverse proxy in front of Send, which they can use to override the
/robots.txt
URL and return whatever content they want. This edit just makes it so that the bare, unsecured Send backend limits search engine access by default.