Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Quotas for file and event storage #3339

Open
matrixbot opened this issue Dec 16, 2023 · 0 comments
Open

Quotas for file and event storage #3339

matrixbot opened this issue Dec 16, 2023 · 0 comments

Comments

@matrixbot
Copy link
Collaborator

matrixbot commented Dec 16, 2023

This issue has been migrated from #3339.


Something that keeps coming up is the need to track which users are responsible for chewing all the storage on your server - whether that's by storing lots of stuff in the media repo, or by joining massive rooms and chewing all your DB (or submitting loads of events).

We probably need to distinguish storage which the user created directly (i.e. by sending a file or event) or indirectly (by accessing a file or a room).

We probably care more about directly attributable storage costs, as indirect ones are going to be shared across a bunch of users - plus tracking the indirect ones could result in a metadata leak for e2e rooms (i.e. which users have access to the files in a given room)

@matrixbot matrixbot changed the title Dummy issue Quotas for file and event storage Dec 21, 2023
@matrixbot matrixbot reopened this Dec 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant