From d58ba079b8fd91b36fba100074168781e22c9373 Mon Sep 17 00:00:00 2001
From: Jon Atkins <github@jonatkins.com>
Date: Sun, 24 Nov 2013 01:32:46 +0000
Subject: [PATCH] COMM: correctly use the ascendingTimestampOrder flag when
 retrieving new COMM messages. this matches the stock intel site, and prevents
 gaps occuring when filling in entries after resuming from idle related to
 #656 no 2

---
 code/chat.js | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/code/chat.js b/code/chat.js
index fc88c670..2c3779fa 100644
--- a/code/chat.js
+++ b/code/chat.js
@@ -106,6 +106,9 @@ window.chat.genPostData = function(isFaction, storageHash, getOlderMsgs) {
     // Currently this edge case is not handled. Let’s see if this is a
     // problem in crowded areas.
     $.extend(data, {minTimestampMs: min});
+    // when requesting with an acutal minimum timestamp, request oldest rather than newest first.
+    // this matches the stock intel site, and ensures no gaps when continuing after an extended idle period
+    if (min > -1) $.extend(data, {ascendingTimestampOrder: true});
   }
   return data;
 }