Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Consider deprecating the age property of events #6999

Closed
richvdh opened this issue Feb 26, 2020 · 3 comments
Closed

Consider deprecating the age property of events #6999

richvdh opened this issue Feb 26, 2020 · 3 comments
Labels
A-Performance Performance, both client-facing and admin-facing A-Spec-Compliance places where synapse does not conform to the spec z-p2 (Deprecated Label)

Comments

@richvdh
Copy link
Member

richvdh commented Feb 26, 2020

Currently most C-S API endpoints include an unsigned["age"] property in each event. This is somewhat annoying to populate on the server (see #6998). Could we kill it off?

@turt2live
Copy link
Member

ftr the spec says it's optional, but I believe at least riot relies on it existing for voip stuff when the client's time is wrong (but that could probably be made a problem for the user to deal with instead of us relying on the server's time)

@neilisfragile neilisfragile added A-Performance Performance, both client-facing and admin-facing A-Spec-Compliance places where synapse does not conform to the spec z-p2 (Deprecated Label) labels Mar 9, 2020
@richvdh richvdh added A-Performance Performance, both client-facing and admin-facing and removed A-Performance Performance, both client-facing and admin-facing labels Oct 21, 2020
@richvdh
Copy link
Member Author

richvdh commented Oct 21, 2020

see also #8429: it probably doesn't even work.

@richvdh
Copy link
Member Author

richvdh commented May 25, 2022

It seems like nowadays, it's actually specced.

@richvdh richvdh closed this as completed May 25, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-Performance Performance, both client-facing and admin-facing A-Spec-Compliance places where synapse does not conform to the spec z-p2 (Deprecated Label)
Projects
None yet
Development

No branches or pull requests

3 participants