1. 14 May, 2019 3 commits
  2. 13 May, 2019 6 commits
  3. 11 May, 2019 1 commit
  4. 10 May, 2019 12 commits
  5. 09 May, 2019 2 commits
  6. 08 May, 2019 2 commits
  7. 07 May, 2019 2 commits
  8. 06 May, 2019 5 commits
  9. 05 May, 2019 1 commit
    • laszlovl's avatar
      Make sure the time attribute for MAM message is parsed through moment · 565f7d9f
      laszlovl authored
      Messages (received directly or via MAM) are stored in a backbone
      collection that's kept sorted by the message's "time" attribute.
      Various parts of the codebase rely on this behavior.
      
      For regular messages, the time attribute is generated by
      `moment().format()`, which generates a timestamp in the browser's
      local timezone, for example "...+02:00".
      
      For MAM messages, we would previously copy the "delay.stamp" value
      into the "time" attribute verbatim. However, that value is generated
      by the server and is unlikely to be in the same timezone locale.
      
      ISO timestamps expressed in different timezones cannot be sorted
      lexicographically, breaking the premise of keeping the messages
      collection sorted by time.
      565f7d9f
  10. 03 May, 2019 6 commits