Pastas should get a field expires_at which indicates it should be destroyed at a specific date & time.

Must have:

• Web UI: A datetime-local input.
• API: An expires_at field should be accepted.
• Backend: Support for both of the above.

Nice to have:

• Web UI: A nice, styled datetime picker instead of browser implementation.
• Web UI/API/Backend: Y2K38 & Y10k problems should be taken into account. Who knows how long this will survive.

Pastas should be able to be flagged as "burn on read". This should permanently delete the pasta after either opening in the Web UI or requesting via the API.

This should be only possible on private (encrypted) pastas to prevent malicious database optimization.

Pasta's right now have no parents; when you click Update on an existing pasta, it's really just creating a new pasta that's not connected to anything.

Must have:

• Backend: Pastas should have information about their parent ID.
• WebUI: Pastas get marked as children when creating a new pasta via the Update button.
• API: Should accept parent_id on the creation endpoint to indicate that we're building upon a parent and not creating a new pasta.
• WebUI/API: If there's information about pasta's parent transmitted to the user, it shouldn't contain secrets - only UUID, no passwords.
• Backend: Parents and children can have different passwords, must have different salts.
• Backend: If the parent is deleted/expired, children should have their parent_id changed to null.
• Backend: Each pasta can have zero or one parent; Any deletion/expiration in the hierarchy should break the tree.
• Backend: A new pasta created via Update should not change parents updated_at.

Nice to have:

• Web UI/API: A button and an endpoint to show diffs would be great.