Michael Kirk fcbfde3874 nonblocking SN change notifications don't percolate group threads to the ... top unless there is a message in that thread. Otherwise the user is overwhelmed by a bunch of group threads with redundant notifications. The notifications will be there if the user later enters the threads. The affect is that only the thread with the relevant message will pop to the top. // FREEBIE		2017-05-19 11:40:44 -04:00
..
Account	Retry push token registration.	2017-05-17 14:26:51 -04:00
Contacts	nonblocking SN change notifications don't percolate group threads to the	2017-05-19 11:40:44 -04:00
Devices	Rework the “disappearing messages” logic.	2017-05-10 14:54:15 -04:00
Messages	Revert "Merge branch 'charlesmchen/autoMarkAsRead'"	2017-05-12 16:21:46 -04:00
Network	nullability audit for MimeTypeUtil	2017-05-04 17:48:00 -04:00
Protocols	Use SignalAccount class to sync contacts.	2017-05-05 20:53:09 -04:00
Security	fix more compiler warnings	2017-05-04 17:56:55 -04:00
Storage	nonblocking SN change notifications don't percolate group threads to the	2017-05-19 11:40:44 -04:00
Util	Rework the “disappearing messages” logic.	2017-05-10 14:54:15 -04:00
TextSecureKitEnv.h	MessageSender should be accessed as singleton	2017-03-30 12:48:36 -04:00
TextSecureKitEnv.m	MessageSender should be accessed as singleton	2017-03-30 12:48:36 -04:00
TSConstants.h	Add SignalAccount class.	2017-05-01 12:46:59 -04:00
TSPrefix.h	Move iOS Versions from Signal-iOS	2017-04-06 16:26:19 -04:00