Methmine Browser
Storage
What this installation is holding, and what of it will stop being readable.
What the screen shows
Totals for the installation at the top: what is on disk, how many snapshots, what is expiring and how many objects are unreferenced. Under them, the table Snapshots by profile, sorted by size, by snapshots or by name.
- Profile
- Name and folder. Every profile holds its own sealed objects; nothing is shared between them.
- Size
- What the profile takes on disk. Sizes are read from the snapshot manifest rather than measured, and nothing was decrypted to total them.
- Snapshots
- Points you can roll back to. Rolling back adds a new point, and the state you rolled back from stays in the list.
- Oldest
- The age of the profile’s oldest snapshot.
- Expiring
- What is past its retention or about to be. The newest snapshot of every profile survives any clean-up.
- Unreferenced
- Objects no snapshot points at any more. Removing them cannot cost a restore point.
Retention
Login state lives thirty days, history twenty-six weeks. When a key expires, what it sealed stops being readable, by us as much as by anyone. That is the design, not a side effect of it. An expired key does not erase the bytes: they stay counted on the disk until a clean-up removes them.
What you do here
- See what takes space and when it expires, per profile and for the installation as a whole.
- Remove expired: snapshots past their window and unreferenced objects go; cookies and history inside a live profile are untouched.
- When nothing is past its window and nothing is unreferenced, the screen says so: there is nothing to clean up.