fix: check if user is affiliated with non-spam community to show profile#3599
Merged
fix: check if user is affiliated with non-spam community to show profile#3599
Conversation
isTravis
approved these changes
Apr 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue(s) Resolved
We implemented a check a while back to only show the profile page of users affiliated to a community to reduce the incentive to create spam users in order to get a visible page where you could post links on.
However, we didn't check whether the community was an approved community or not, which lead to at least one bot creating a ton of spam communities to create a public profile page.
THis PR remedies that and includes a check whether said community is actually approved or not.
Additionally it gives superadmins a bit more context when looking at an otherwise non-public user profile page.
Test Plan
Screenshots (if applicable)
Optional
Notes/Context/Gotchas
Supporting Docs