Shapshots should contain date about peer-pad HOT 9 CLOSED

Yes, since each snapshot has it's own independent decryption key. Access to these doesn't compromise the "future" of the document.

from peer-pad.

@diasdavid @pgte the list of snapshots for a doc are lost when the user refreshes the page, and we don't currently have timestamp info on the objects. Do you want the UI to add them to localstorage / or is it a peerpad-core responsibility?

from peer-pad.

Right now peerpad-core only takes the snapshot, so it's up to the app to do whatever with it.
(Later on we plan to store docs and have a directory view, but right now that's still a bit fuzzy.. (at least for me)).

from peer-pad.

@olizilla while you're at it, could you please make the hash link open in a new window?

from peer-pad.

👍

note to self: fix #54 while we're in here.

from peer-pad.

@pgte It is ok to store the snapshot hash and key in localStorage? I know this is an alpha with no security promises, but I still wanted to check.

from peer-pad.

@pgte last question! Snapshots need to be keyed on current document, so I know which ones to load when we render a new pad. Is it sensible to use the readKey for the current doc, since the name is mutable.

from peer-pad.

The document name should not change, you're probably thinking about the document title, so it's safe.

In regards to the document title changing, let's track this on another issue, I've neglected this part.

from peer-pad.

Ah, I think name and title are currently conflated in the UI. name is plucked from the the url, set as state, and then mutated when the user edits the title. I'll pull them apart.

from peer-pad.