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

Setting community.hidden should be part of CommunityVisibility enum #5458

Open
Nutomic opened this issue Feb 27, 2025 · 5 comments
Open

Setting community.hidden should be part of CommunityVisibility enum #5458

Nutomic opened this issue Feb 27, 2025 · 5 comments
Labels
enhancement New feature or request
Milestone

Comments

@Nutomic
Copy link
Member

Nutomic commented Feb 27, 2025

Hiding a community from all feed is also a type of visibility, so it makes sense to merge all of them into the same setting. This will also make it easier to show the setting in the ui, as its just another dropdown option. Have to see how exactly this should federate.

@Nutomic Nutomic added the bug Something isn't working label Feb 27, 2025
@Nutomic Nutomic added this to the 1.0.0 milestone Feb 27, 2025
@Nutomic Nutomic added enhancement New feature or request and removed bug Something isn't working labels Feb 27, 2025
@dessalines
Copy link
Member

I think private should probably be separated out instead. Then the enum could be Public, LocalOnly, or Hidden, with private being optional for all those.

@Nutomic
Copy link
Member Author

Nutomic commented Feb 28, 2025

For UX it makes a lot of sense to have all these as part of the same visibility setting, and its also easier to implement. Otherwise its ambiguous what a private + public, or private + hidden community would mean.

@dessalines
Copy link
Member

Private seems to be about approval anyway. It looks like there's already a ApprovalRequired on subscribedtype. Is there any difference between these?

@Nutomic
Copy link
Member Author

Nutomic commented Feb 28, 2025

ApprovalRequired is the one used by private community.

@dessalines
Copy link
Member

IMO that should be moved to its own column then (either private, or approval_required). Because then you can have a Public or LocalOnly community, that requires approval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants