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

/createRoom API behaviour does not match spec #3488

Open
t3chguy opened this issue Jan 7, 2025 · 0 comments
Open

/createRoom API behaviour does not match spec #3488

t3chguy opened this issue Jan 7, 2025 · 0 comments
Labels
good first issue Good for newcomers spec-compliance Fix something that doesn't comply with the specs T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.

Comments

@t3chguy
Copy link
Member

t3chguy commented Jan 7, 2025

Background information

  • Dendrite version or git SHA: docker main
  • SQLite3 or Postgres?: sqlite3
  • Running in Docker?: yes
  • go version: docker main
  • Client used (if applicable): matrix-js-sdk

Description

  • What is the problem: /createRoom API uses join_rule=invite if preset is unspecified even if visibility is specified
  • Who is affected: Unclear
  • How is this bug manifesting: Creating rooms unlike the intent of the creator
  • When did this first appear: Unclear

#3123 (comment) for more context

The spec does say to use visibility if preset is unspecified.

If unspecified, the server should use the visibility to determine which preset to use. A visibility of public equates to a preset of public_chat and private visibility equates to a preset of private_chat.

https://spec.matrix.org/v1.13/client-server-api/#post_matrixclientv3createroom

Steps to reproduce

  • call /createRoom API with visibility=public
  • receive a room via /sync which has join_rule=invite instead of join_rule=public
@S7evinK S7evinK added good first issue Good for newcomers spec-compliance Fix something that doesn't comply with the specs T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues. labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers spec-compliance Fix something that doesn't comply with the specs T-Defect Bugs, crashes, hangs, security vulnerabilities, or other reported issues.
Projects
None yet
Development

No branches or pull requests

2 participants