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

MSC3173: Expose stripped state events to any potential joiner #3173

Merged
merged 19 commits into from
Jun 20, 2021

Conversation

clokep
Copy link
Contributor

@clokep clokep commented May 3, 2021

@clokep clokep changed the title [WIP] MSCXXXX: Expose stripped state events to any potential joiner [WIP] MSC3173: Expose stripped state events to any potential joiner May 3, 2021
@turt2live turt2live marked this pull request as draft May 3, 2021 17:37
@turt2live turt2live added client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff proposal A matrix spec change proposal labels May 3, 2021
@clokep clokep mentioned this pull request May 3, 2021
@clokep clokep changed the title [WIP] MSC3173: Expose stripped state events to any potential joiner MSC3173: Expose stripped state events to any potential joiner May 12, 2021
@clokep clokep marked this pull request as ready for review May 12, 2021 14:34
@clokep
Copy link
Contributor Author

clokep commented May 12, 2021

Since this is pretty much a clarification / expansion of current behavior, I don't think this really needs an implementation since...the current implementations already implement this. 😄

@turt2live turt2live added this to Awaiting SCT input in Spec Core Team Backlog via automation May 12, 2021
@turt2live turt2live self-requested a review May 12, 2021 14:37
Copy link
Member

@turt2live turt2live left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall seems sane. It's a bit awkward that the MSC says the user can access the stripped state, but doesn't really describe how the user might encounter those events. Dedicated endpoints are probably still out of scope for this MSC, but some clarification around the unification of stripped state and when they might appear (potentially in future MSCs) would be appreciated.

proposals/3173-expose-stripped-state-events.md Outdated Show resolved Hide resolved
proposals/3173-expose-stripped-state-events.md Outdated Show resolved Hide resolved
proposals/3173-expose-stripped-state-events.md Outdated Show resolved Hide resolved
proposals/3173-expose-stripped-state-events.md Outdated Show resolved Hide resolved
@turt2live turt2live merged commit ecd28fe into master Jun 20, 2021
@turt2live turt2live moved this from In FCP to Done to some definition in Spec Core Team Backlog Jun 20, 2021
@turt2live turt2live added spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec and removed finished-final-comment-period labels Jun 20, 2021
receive stripped state events to display metadata to users.

This MSC proposes formalizing that the stripped state that is currently available
to invited and knocking users is available to any user who could potentially join
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is “potentially join” recursive? I.e., if I'm in A, which allows joining B, which allows joining C, can I potentially join C?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for the purposes of this MSC, no. Recursion like that would be determined in another access control MSC.

@turt2live
Copy link
Member

Spec PR: #3606

@turt2live turt2live added spec-pr-in-review A proposal which has been PR'd against the spec and is in review and removed spec-pr-missing Proposal has been implemented and is being used in the wild but hasn't yet been added to the spec labels Dec 29, 2021
turt2live added a commit that referenced this pull request Jan 5, 2022
* Describe and hoist stripped state to a first-class citizen

Fixes #3413
MSC: #3173

* Add changelog

* may->can for clarity

* Update text per review
@turt2live
Copy link
Member

Merged 🎉

@turt2live turt2live added merged A proposal whose PR has merged into the spec! and removed spec-pr-in-review A proposal which has been PR'd against the spec and is in review labels Jan 5, 2022
@clokep clokep deleted the clokep/stripped-state branch May 17, 2023 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client-server Client-Server API kind:feature MSC for not-core and not-maintenance stuff merged A proposal whose PR has merged into the spec! proposal A matrix spec change proposal
Projects
Spec Core Team Backlog
  
Done to some definition
Development

Successfully merging this pull request may close these issues.

None yet