Skip to content

A first draft of a document describing Matrix state and state resolution#5

Merged
maxidorius merged 3 commits intomasterfrom
magnap/state-first-draft
Nov 11, 2017
Merged

A first draft of a document describing Matrix state and state resolution#5
maxidorius merged 3 commits intomasterfrom
magnap/state-first-draft

Conversation

@Magnap
Copy link
Copy Markdown
Collaborator

@Magnap Magnap commented Nov 10, 2017

No description provided.

@Magnap Magnap self-assigned this Nov 10, 2017
@Magnap Magnap added the state label Nov 10, 2017

* Room state
While the state of a room is an arbitrary set of key-value pairs,
only a certain subset of that state is relevant to federation,
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Note towards implementations: it might happen "internally" also, in case of a master/master setup and the approach taken was to have each node deal with state resolution, instead of trying to keep the exact same view in each node.

for a given auth state,
whether a given auth event represents a valid change.
For the current auth rules,
see [[https://matrix.org/docs/spec/server_server/unstable.html#rules][the official spec]].
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I would point to https://matrix.org/speculator/spec/HEAD/server_server/unstable.html#rules which is the most up-to-date version and the one we would build on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants