Broadcast state change when conversation unarchived

[rthouvenin]

MongooseIM version: 6.2.1

The specifications of the Inbox feature state that when a client requests the archival of a conversation, the server sends a message to the bare jid of the requesting user, so that all clients can be notified of the state change.
The specs also state that when an archived conversation receives a new message, it is automatically unarchived by the server. Shouldn't the server send at this stage a notification about the state change, like after the archival? This would let clients rely on the server for centralising the unarchiving logic. Without this notification, they have to change the state of the local conversation when receiving the new message and assume/hope that the server did the same thing.

What do yo think?

[JanuszJakubiec]

Hi, thank you for your input. We’ll discuss the idea you've presented during our backlog grooming session, where we'll assess its potential implementation in MongooseIM.