question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

all space members are able to see invite only rooms in spaces

See original GitHub issue

Description

After upgrading synapse from 1.34 to 1.35 (debian testing), space members with default power level in the space are able to see invite only rooms in the space’s “Explore rooms”-view that they are not allowed to join.

Steps to reproduce

  • create a private space S with account A
  • add/create a public room P in space S with account A
  • add/create a room R in space S with account A set to:
    • “Who can access this room?”: “Only people who have been invited”
    • “Who can read history?”: “Members only (since they joined)”
  • invite account B to space S

Expected outcome

  • account B is able to see room P in the “Explore rooms”-view of the space
  • account B is not able to see room R in the “Explore rooms”-view

Actual outcome

  • account B is able to see room P in the “Explore rooms”-view and is able to join it.
  • account B is able to see room R in the “Explore rooms”-view. However, when trying to join, account b is presented with the error message: Failed to join room You are not invited to this room.

As per https://gist.github.com/t3chguy/fdf541446d992d1fc96b8089b342fe7b#gistcomment-3755026, this does not seem to be the intended behavior.

Version information

  • Homeserver: matrix.pack.rocks (ran by me)
  • Version: 1.35.0+bullseye1
  • Install method: debs from https://matrix.org/packages/debian/
  • Platform: qemu-VM on Debian 11, no containers involved
  • Default Room Version: 6 I did set experimental_features: { spaces_enabled: true } in /etc/matrix-synapse/homeserver.yaml in 1.34 which is still present. Removing it does not change the behavior described above.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:13 (7 by maintainers)

github_iconTop GitHub Comments

3reactions
clokepcommented, Jun 2, 2021

The plan is to do a v1.35.1 release with the fix for this tomorrow. Thanks for reporting!

2reactions
clokepcommented, Jun 2, 2021

@herbetom It is being actively worked on.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Space Sharing + Accessibility - Spatial
If an invitee does not have a Spatial account, they will join the space as a guest. Guest users can navigate around the...
Read more >
Users joining a private room within a space via "restricted" join ...
Create a space · Create a private room in that space · Confirm that history visibility is set to shared · Set its...
Read more >
About spaces and group conversations - Google Chat Help
You can use spaces or group conversations in Google Chat to communicate with one or more people. Spaces: A central place where people...
Read more >
About Twitter Spaces
Spaces are public, so anyone can join as a listener, including people who don't follow you. Listeners can be directly invited into a...
Read more >
Spaces: The next frontier - Element
What's next? · Auto-joining rooms when joining a Space— to ensure visitors or members see and participate in the same communal rooms. ·...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found