Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change private instance setting to allow federation #5530

Merged
merged 1 commit into from
Mar 28, 2025

Conversation

Nutomic
Copy link
Member

@Nutomic Nutomic commented Mar 24, 2025

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.

Copy link
Member

@dessalines dessalines left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with removing this, especially since federation_enabled is already its own setting.

@Nutomic Nutomic merged commit e079a41 into main Mar 28, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants