In a public Discourse instance with mixed public and private categories, meglio seeks to ensure anonymous users cannot list all users via API or UI—even with user directory disabled and profiles hidden. Falco clarifies that while disabling the user directory hides the leaderboard, users can still be listed via API unless login is required. meglio confirms concern is about full exposure to anonymous users, and Falco confirms this is current behavior. meglio suggests a feature request to block user listing while keeping public categories; Falco notes such a change would be niche and labor-intensive, recommending the Marketplace for funding. merefield questions whether hiding user lists is meaningful given exposure through public topics, and meglio explains their use case involves a small public contributor group within a larger private team. merefield concludes that for full privacy, running two separate instances may be the only practical solution—though no sensitive data like emails is exposed.
Depends on what you mean exactly by “exposing” users. Any user that posts in the public category will be public, and then it depends on what percentage of your users will interact in that specific category.
I mean for an anonymous user to reveal the list of users. Like e.g. listing all users through API, or seeing the list in “Top Users”, or through Search function, or in any other way that I’m unaware of.
Is that because it’s considered futile to hide that data if stuff is understandably exposed in unpredictable amounts from public topic lists in any case?
I don’t think anyone planned it so much, it’s more that Discourse has two basic modes: public and private. The setting to hide the leaderboard does exactly what it says, it hides the leaderboard. Why would it do something extra?
Feel free to write up an spec of what you want, but as it’s a very boring work to do and such a niche use case you would have more luck posting it to the Marketplace if you want to see it anytime soon.