Papyr Write together in Markdown. The server can't read it. Try it GitHub

Plenum 0.2.0

What it does new

  • A sealed room may expire: the start page’s “New sealed room” offers 1 hour, 1 day, 1 week, 30 days or never. The expiry is part of the link (/r#s.<secret>.<expiry>) and of the room’s id, so nobody can change it. From that moment nobody joins the room, and within the hour after it the server closes it and removes its files (docs/operations.md, “Expiry”). Plenum:RoomExpiryDays still removes rooms nobody wrote to; whichever comes first. The admin API lists each room’s expires; the metric plenum.room.expired carries the reason (idle or expired), and event 39 logs a room removed at its expiry (docs/telemetry.md).

What to change

This release breaks the relay contract (version 3) and the room files (format 4):

  • Delete the stored rooms before you upgrade. Every room id changes (it covers the expiry), so every room stored by an earlier version is new to this one, and the server does not start on files of an earlier format: export the texts you want to keep (a room’s More, Export) with the old image, stop it, remove rooms/*.log, rooms/*.snapshot and rooms/*.tmp, start the new image, import the texts (docs/self-hosting.md, “Upgrading”). Backups of an earlier version cannot be restored.
  • Links keep working: a link without an expiry derives the same keys, and opens an empty room on the new server.
  • Pages of the earlier version still open are told to reload (4009).
  • A client written against the contract: the hello is 42 bytes (4, 3, the access key, the expiry), both HKDF derivations take the expiry’s 8 bytes as their salt, the room id is the SHA-256 of the access key and the expiry, and 4011 means the room expired (spec/relay-protocol.md, spec/protocol-vectors.json).
  • The admin API’s room has a new member, expires.