You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, it's the Timeline API that takes care of retrying decryption of an event. This has a few bad consequences:
retrying decryption, while it could be done in other contexts than the Timeline API, can only happen there
some observers (e.g. the UTD hook) want to know when a previously-UTD event could be decrypted; this happens in the Timeline code too, which is an abstraction leak
some other code basically retries decryption on its own: the latest event code in the base crate does that
I'm proposing that we move all of this over to the Event Cache. An event in a linked chunk / on disk would be replaced by its decrypted equivalent, if needs be, and we can implement a few enhancements mentioned in a few other issues too.
After re-decrypting an event correctly, emit a new kind of room event cache update for the decrypted event
store the decrypted event back into the in-memory linked chunk (and storage too)
Right now, it's the Timeline API that takes care of retrying decryption of an event. This has a few bad consequences:
I'm proposing that we move all of this over to the Event Cache. An event in a linked chunk / on disk would be replaced by its decrypted equivalent, if needs be, and we can implement a few enhancements mentioned in a few other issues too.
latest event
logic in there, and remove it from the base cratePart of #3058.
The text was updated successfully, but these errors were encountered: