Change private instance setting to allow federation #5530
Merged
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.
The
private instance
setting makes it so that only logged-in users can browse posts. It also includes a check which requires that federation is disabled. The idea was that content on such instances should be truly private, and not publicly visible on other instances.Now that there is a setting for community visibility: private, making the whole instance private isnt really necessary anymore. By allowing "private instance" with federation enabled, it can be used to fight of AI crawlers or DDoS attacks as they cannot access any content anymore. At the same time there is no change for logged-in users. We could change the setting name at the same time if there is a better suggestion.
cc @db0 This is the "raid mode" you were talking about.