Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Expose DAG to clients #819

Closed
Lapin0t opened this issue Mar 1, 2017 · 4 comments
Closed

Expose DAG to clients #819

Lapin0t opened this issue Mar 1, 2017 · 4 comments
Labels
feature Suggestion for a significant extension which needs considerable consideration

Comments

@Lapin0t
Copy link

Lapin0t commented Mar 1, 2017

It would be really nice for a lot of applications of matrix to expose the underlying DAG of events within a room. Some usecases:

  • clients can order the events how they wish (topological sort is not unique) or even display the links in the UI
  • applications could begin using matrix as a generic distributed database for partially ordered messages (collaborative document edition, key-value stores, ...)

A proposal to expose the links: add a new field to all events containing a list of event ids. It could be named parents.

@dumblob
Copy link

dumblob commented Jan 29, 2018

ping

@maxidorius
Copy link
Contributor

The spec already defines a way via sync filters to get the full events, including parents, auth events, etc.

@turt2live turt2live added the feature Suggestion for a significant extension which needs considerable consideration label Jul 19, 2018
@turt2live
Copy link
Member

Now that the sync filter actually works in (develop) synapse, and the thing is possible for clients to use, I think this can be closed.

@ara4n
Copy link
Member

ara4n commented Sep 7, 2018

i’m not sure the ability to request federation event fields via cs api is entirely deliberate, fwiw. but if it works...

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
feature Suggestion for a significant extension which needs considerable consideration
Projects
None yet
Development

No branches or pull requests

5 participants