Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I have a use case where I want to be able to easily get the set of indexed events older than a specified age.
I want to do this so I am able to delete from the index events that have been automatically deleted by the homeserver after their retention period but may remain inside the index since no redaction event is issued by the server (I think ?).
The scenario I want to avoid is if a seshat index gets fully compromised, the attacker may access the entire history, even events that expired due to room/server retention.
This PR aims to later be able to control a retention period on the client.
I will work on an async version of this next week but I am still taking feedbacks on this.