Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Delight: What if users to join a space in their first session? #515

Closed
daniellekirkwood opened this issue May 4, 2022 · 8 comments
Closed

Comments

@daniellekirkwood
Copy link
Contributor

daniellekirkwood commented May 4, 2022

HMW support a user wishing to join a space in their first session?

The Delight team are exploring options for this in Q2 and Q3 of 2022 as part of the larger New user Journey epic

@duxovni
Copy link

duxovni commented May 4, 2022

(Marking this as "Needs Info" for the Web team triage since I'm not clear on what the proposal is, but if this is mostly a note-to-self and you're already handling it, then no worries)

@duxovni duxovni added the X-Needs-Info This issue is blocked awaiting information from the reporter label May 4, 2022
@daniellekirkwood
Copy link
Contributor Author

(Marking this as "Needs Info" for the Web team triage since I'm not clear on what the proposal is, but if this is mostly a note-to-self and you're already handling it, then no worries)

Thank you! Yes, I created this as an empty issue and will add more info asap. Still, let's leave the label on it!

@daniellekirkwood
Copy link
Contributor Author

"should explore ways to give homeserver admins an easy way from GUI to setup auto-join rooms when registering...

But this means exposing some admin functionality from a standardised API (which means we need to go through an MSC \o/ )"

@t3chguy
Copy link
Member

t3chguy commented May 12, 2022

Given auto-join rooms is a Synapse-specific concept, it isn't something we should be doing. The Matrix Spec doesn't really have a concept of homeserver admins so adding features specifically for them becomes much harder as first you'd need to MSC that.

@germain-gg
Copy link

The foundations of an administration API exists as part of matrix-org/matrix-spec-proposals#3593 but this MSC's scope is probably a bit too large for what we'd like to do.

Another interesting thing to note is that the auto room join config lives in synapses yaml config, which requires a synapse restart to be picked up.

The synapse admin management is not really standardised at the moment. We should be able to add a way to manage that in the EMS management console but this will not solve the problem holistically
Projects like https://github.com/Awesome-Technologies/synapse-admin would also need to be considered if we're looking to have a broader impact

A good way to validate our theories here, is to apply those changes on the large public homeserver by suggesting some configuration to admins and watch metrics that we can gather from there

@turt2live
Copy link
Member

@daniellekirkwood can we get an update on this issue please? The description is still blank, and queued for closing.

@daniellekirkwood
Copy link
Contributor Author

Sure. Why is it queued for closing?

@daniellekirkwood daniellekirkwood added X-Needs-Design X-Needs-Product More input needed from the Product team labels Jun 14, 2022
@t3chguy
Copy link
Member

t3chguy commented Jun 14, 2022

@daniellekirkwood because it has been marked as Needs Info for a month

@daniellekirkwood daniellekirkwood removed the X-Needs-Info This issue is blocked awaiting information from the reporter label Jun 14, 2022
@daniellekirkwood daniellekirkwood transferred this issue from element-hq/element-web Jul 19, 2022
@element-hq element-hq locked and limited conversation to collaborators Jul 19, 2022
@daniellekirkwood daniellekirkwood converted this issue into discussion #516 Jul 19, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Projects
None yet
Development

No branches or pull requests

5 participants