-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Consenting to terms as a guest while joining a room leaves you stranded #14584
Comments
I'm trying to switch a community I run over to riot/element and we are experience a lot of these issues too. Guest accounts in general feel like they aren't even meant to be a part of the experience right now. From my side I've experienced:
|
Additionally, when testing this, I found that navigating to http://localhost:8080/#/room/#some-room:localhost without being logged in created a guest account on matrix.org, even though the room only existed on my local HS, and Element's
|
Not related to #11655, that one is about Element validating its config against the well-known of the config HS (matrix.org) |
@anoadragon453 is it possible the guest already existed from an earlier session where your config.json was different? Can you reproduce it incognito? The client won't create a new guest if it already has one even if the default HS in the config changed since its inception. I can't reproduce it here. I set my config.json to riot.ovh and when loading incognito I see a failure to register a guest due to my server's guest access being disabled. |
given fosdem wants to use guests, this could do with some urgent attention, cc @jryans |
From chatting with @ara4n in more detail, it seems like FOSDEM's core use case of joining a room directly actually works okay and avoids the hoops recorded in this issue. In any case, since we're on the topic, I'll try reproducing and fixing what I find in this area. |
Similar to @t3chguy, I can't replicate this issue: the guest account is created on Element's default server. |
I am not sure which path was tested here, but if you join a guests can join room, you can write in it. It's slightly unclear whether Element actually intends for you to be able to join a room as a guest at the moment though, see #16037.
I can't reproduce this, please file a separate issue with more detailed steps. In my testing, "join" from the the directory joins for real, while the room preview bar wants you to register, which is another aspect of #16037. |
This is the main thing listed here that still exists (that I can replicate at least). At the moment, if you happen to need to consent to terms as a guest user to do some action (most likely joining), we do not remember what action you were trying to perform after you consent. This issue does not exist for normal (non-guest) users since require them to consent as a registration step.
This part sounds like mostly slow server performance...? I haven't been able to replicate, so a separate issue with video might be needed.
Not sure what happened there, probably some unrelated thing.
This has been "fixed" by changing the user menu to only allow "signing in as another account" if you are a guest. There is no sign out any more. |
Since the main remaining problem that still exists from this issue is part related to consent on join leaving you a bit lost, I have restructured the issue to focus on that. |
hi. thanks for taking a look at this. I've noticed that it's not possible to follow an invite as guest. (Join a room as guest, get invited to DM by someone else, trying to follow this invite as guest fails.) I only found this issue that was similar so I subscribed here. Shall I create a new ticket for this? |
Yes, please make a new issue, it's generally easier to track things that way, especially once fixes are in motion. |
okay: #16164 |
As of matrix-org/matrix-react-sdk@3115c4f, we have changed the room directory to only show preview buttons to guest users, so I believe this flow is no longer possible to reach. Given that, I'll close this issue. |
. What do I do now? I'm certainly not in HQ, either way.
@jryans: These bits no longer reproduce / can't be actioned:
The text was updated successfully, but these errors were encountered: