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

Public Rooms cannot be found on Snikket servers when the searching user has an account on a different server #234

Open
p42ity opened this issue Sep 28, 2024 · 1 comment

Comments

@p42ity
Copy link
Contributor

p42ity commented Sep 28, 2024

If a user has an account on example.ORG and searches for public rooms on a different Snikket server (e.g. example.COM), this user cannot find any public rooms (even if there are public rooms). People on example.com can find public rooms on example.com.

@Zash has identified that this behavior changed because of: #199

Might be related to: https://issues.prosody.im/1866

Is this a wanted behaviour or is this a bug?

@mwild1
Copy link
Member

mwild1 commented Sep 28, 2024

It was something I was moving towards, though the change was unintentional for this release.

As mentioned in the past, Snikket instances/apps are not really designed for hosting public channels (which need moderation tooling, etc.), and we have also had cases of people unintentionally creating public channels, with the assumption that they are private.

This new behaviour is a safer default, though I was still internally debating what kind of overrides we would have for it, if any. This partially applies to Prosody, too, though of course behaviour will ultimately be fully configurable there.

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

No branches or pull requests

2 participants