Message lifetimes

[Biep]

This issue, described here, has both a server and a client component.

[turt2live]

Closing in favour of MSC: matrix-org/matrix-spec-proposals#2228

[Biep]

Doesn't that do way less? Or do you mean the rest of my proposal can be done client-only?
My proposal would be that delivery time can be done on the server - no need to have the client running at the moment that the server needs to deliver the message. In fact, my reason for using future delivery may be precisely because I know my device will be off-line when delivery is needed.

[turt2live]

The MSC is the same sort of system you described in your other issue, so would recommend leaving any concerns you have with the MSC on the MSC.

[Biep]

I have seen the abbreviation, but do not know what "MSC" means. "Matrix-spec-?".
I had made proposals for Element Web / Desktop, was asked to move them if I was still interested, and did move them.
Did I do something wrong?

[turt2live]

Matrix Spec Change: https://spec.matrix.org/unstable/proposals/

Moving issues to more appropriate repos is fine, however it doesn't guarantee that the issue stays open. For the spec we try to consider whether an issue is likely to be actioned or able to be actioned when deciding if it stays open or not. In this issue's case, there's already an MSC opened which talks about the feature so we'd prefer to have discussions there.

Edit: wrong issue context.