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.

Sign up for GitHub

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

Jump to bottom

We need a nice table showing how to interpret m.room.member events #876

Closed
ara4n opened this issue Apr 1, 2017 · 1 comment · Fixed by #2056
Closed

We need a nice table showing how to interpret m.room.member events #876

ara4n opened this issue Apr 1, 2017 · 1 comment · Fixed by #2056
Assignees
@turt2live
Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API
Projects
Matrix 1.0 workflow

Comments

@ara4n
Copy link
Member

ara4n commented Apr 1, 2017

One axis would show possible prev_content values; the other would show possible content values; and explain that join->join is a profile change, join->leave is either a leave or a kick, join->ban is a kickban, leave->ban is a ban, etc.
@t3chguy
Copy link
Member

t3chguy commented Aug 28, 2017

Initial: https://docs.google.com/spreadsheets/d/1jNZyt53RrvwnyPulJA0wUTTXFynS1pB6twPoUu0SUUI/edit?usp=sharing

@turt2live turt2live added the clarification An area where the spec could do with being more explicit label Jul 9, 2018
@turt2live turt2live added the client-server Client-Server API label Sep 6, 2018
@turt2live turt2live added this to Nice to have clarifications in Matrix 1.0 workflow May 25, 2019
@turt2live turt2live self-assigned this May 30, 2019
@turt2live turt2live moved this from Clarifications TODO to In progress in Matrix 1.0 workflow May 30, 2019
turt2live added a commit that referenced this issue May 30, 2019
@turt2live
Add a table to show how changes in membership should be interpreted
f3c0c52 
Fixes #876
@turt2live turt2live mentioned this issue May 30, 2019
Merged
Matrix 1.0 workflow automation moved this from In progress to Done Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@turt2live turt2live

Labels
clarification An area where the spec could do with being more explicit client-server Client-Server API
Projects
No open projects
Matrix 1.0 workflow
  
Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add a table to show how changes in membership should be interpreted matrix-org/matrix-spec-proposals
3 participants
@turt2live @ara4n @t3chguy