Conversation history in the SVS

[redshiftzero]

Journalist A is a user of SecureDrop and is communicating with a source. However, journalist A is also quite a busy person and forgets exactly what they have said N days or even weeks ago. Bad news: unless they are organized and they are keeping a nice list of replies in a folder on the SVS, they must rely on their memory. However, this conversation history could be tracked in a more organized way automatically in an interface based on #415. Obviously a usability-security tradeoff here, so documentation should accompany this to encourage journalists to totally delete a conversation when they are done.

[ghost]

Maybe the reply could be encrypted for both the source and the submission key so the journalist can decrypt it afterwards and read their reply?

[redshiftzero]

Being addressed over in #3097 (and in issues in the securedrop-client repo), closing in favor of those more specific issues