From 03c5d12edd7dc82b1131b435efef05fcd8deeec0 Mon Sep 17 00:00:00 2001
From: lilia <liliakai@gmail.com>
Date: Wed, 12 Oct 2016 11:10:21 +0900
Subject: [PATCH] Fix necrobumping convos on key change

When inserting key change advisories, use the current conversation
timestamp to avoid pushing lots of old groups to the top of the
conversation list.
---
 js/models/conversations.js | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/js/models/conversations.js b/js/models/conversations.js
index afe707b502..aa7c547264 100644
--- a/js/models/conversations.js
+++ b/js/models/conversations.js
@@ -51,12 +51,11 @@
     },
 
     addKeyChange: function(id) {
-        var now = Date.now();
         var message = this.messageCollection.add({
             conversationId : this.id,
             type           : 'keychange',
-            sent_at        : now,
-            received_at    : now,
+            sent_at        : this.get('timestamp'),
+            received_at    : this.get('timestamp'),
             key_changed    : id
         });
         message.save();