Deal with "outdated" conversations

[tiltec]

Pickup and application conversations currently stay around forever, although the conversation target has an end. Especially in the case of application conversations it can be confusing if people reply to an application that already has been decided.

My proposal would be to close application and pickup conversations a few hours after the conversation target has ended. We would need to show information to the user about this behavior.

The alternative could be to close the conversation some hours after the last reply, to not cut off an active discussion.

[nicksellen]

Ah the alternative idea sounds possibly like a smart way of dealing with it, it would need both criteria being fulfilled:

1. the target has "ended" (whatever that means for the target)
2. x hours has passed since last reply

If only 1) was implemented it will still check x hours since the target has ended, so adding 2) is not much more (referencing the time to the last reply rather than the target).

[tiltec]

I would add an ended property to conversation targets and search for ended targets in a cronjob. If the last reply was more than 7 days ago, mark the conversation as "closed".