Per-user Media storage quota #132
Labels
No labels
kind
bug
kind
enhancement
wayfinder
grilling
wayfinder
map
wayfinder
prototype
wayfinder
research
wayfinder
task
workflow
needs-info
workflow
needs-triage
workflow
ready-for-agent
workflow
ready-for-human
workflow
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rosa/vernier#132
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Per-user Media storage quota
Deferred from #131. Media is stored as BLOBs in the single SQLite file
(ADR-0017) and orphans are tolerated (ADR-0017 / #131), so uploads only ever
grow the file. v1 ships with a per-upload size cap and the optimization step as
the only bounds — no per-user total-storage quota.
Why deferred: users are invite-only and semi-trusted (
CONTEXT.md), anOperator can delete an abusive User (cascading their Media away), and quota is
real machinery (accounting, enforcement, surfacing the limit). Disproportionate
for a small self-hosted instance in v1.
Signal to revisit: DB file size becoming an operational concern — mirroring
how ADR-0016 frames "revisit when write volume outgrows a single writer."
Deferred: per-user Media storage quotato Per-user Media storage quota