William Grant
|
1d7380a254
|
refactor: rename expirationLength
to expirationDurationMs
|
2 years ago |
|
William Grant
|
f3b4b6f862
|
refactor: isDisappearing to matchesDisappearing
cleaned up some comments
|
2 years ago |
|
William Grant
|
8d9fc33180
|
fix: remove unnecessary async on markReadNoCommit
|
2 years ago |
|
William Grant
|
7b8d1ed2f7
|
fix: replace backbone get method
for lastDisappearingMessageChangeTimestamp
|
2 years ago |
|
William Grant
|
5f3a0899f5
|
feat: moved remaining code into feature folder
also separated out legacy functions
|
2 years ago |
|
William Grant
|
0212166fcc
|
feat: moved disappearing logic to a feature folder
only moved types and timerOptions so far
|
2 years ago |
|
William Grant
|
cafa9d80ec
|
fix: remove all unneeded tslint comments
fixed some eslint errors
|
2 years ago |
|
William Grant
|
06099966b0
|
fix: make sure to use convo getters
instead of backbone get function
|
2 years ago |
|
William Grant
|
12a29f718a
|
feat: updateExpireTimer arg shouldCommitMessage
when testing we dont want to commit the timer update message
|
2 years ago |
|
William Grant
|
6f78de0ed3
|
feat: made ExpirationTimerUpdate type
|
2 years ago |
|
William Grant
|
769808bd5c
|
test: finished changeToDisappearingMessageType tests
|
2 years ago |
|
William Grant
|
37bdd08aca
|
fix: correct getter region comments
|
2 years ago |
|
William Grant
|
caf39d661c
|
feat: commit disappearing remote changes to db
|
2 years ago |
|
William Grant
|
27a634b268
|
feat: updateExpireTimer now returns success
we use this to decide on commiting updates from sync messages to the db
|
2 years ago |
|
William Grant
|
5b7afe0a29
|
fix: disappear synced settings updates
need to trigger the expirationStartTimestamp manually
|
2 years ago |
|
William Grant
|
bb646ed3b9
|
refactor: replaced get expirationTimerUpdate calls
with getExpirationTimerUpdate
|
2 years ago |
|
William Grant
|
0dcf48be16
|
refactor: replaced get expires_at calls
with getExpiresAt
|
2 years ago |
|
William Grant
|
61eccb8d0f
|
refactor: replaced get expirationStartTimestamp calls
with getExpirationStartTimestamp
|
2 years ago |
|
William Grant
|
777584945d
|
refactor: replaced get expireTimer calls
with getExpireTimer
|
2 years ago |
|
William Grant
|
ebaedb2e4c
|
feat: created getters in message model
replaced all expirationType calls with getExpirationType
|
2 years ago |
|
William Grant
|
1861131ce2
|
refactor: replaced get lastDisappearingMessageChangeTimestamp calls
with getLastDisappearingMessageChangeTimestamp
|
2 years ago |
|
William Grant
|
712a1e92e4
|
refactor: replaced get hasOutdatedClient calls
with getHasOudatedClient
|
2 years ago |
|
William Grant
|
f31e157c12
|
refactor: replaced get expireTimer calls
with getExpireTimer
|
2 years ago |
|
William Grant
|
3ed041c4a5
|
feat: created getters on convo model
replaced all expirationMode calls
|
2 years ago |
|
William Grant
|
38a8012e10
|
refactor: providedexpirationtype to provideddisappearingmode
|
2 years ago |
|
William Grant
|
a484011acb
|
refactor: changetodisappearingmessageconversationtype to changetodisappearingconversationmode
|
2 years ago |
|
William Grant
|
250e3d0238
|
refactor: rename expirationType on convo to expirationMode
this means convo has expirationMode and messages have expirationType
|
2 years ago |
|
William Grant
|
cd2f51684d
|
refactor: disappearingmessageconversationtype to disappearingmessageconversationmodetype
|
2 years ago |
|
William Grant
|
93b450ce56
|
feat: hit expire endpoint for read messages
for now it will hit the expire endpoint twice
|
2 years ago |
|
William Grant
|
c1dc2e5a6c
|
fix: hit expire endpoint when send is successful
we need the returned messageHash from the swarm
|
2 years ago |
|
William Grant
|
a4bd3f59bb
|
feat: improved expire swarm result logic
better logging and handle errors more smoothly
|
2 years ago |
|
William Grant
|
beb04d1b31
|
feat: improved logging for start expiry timestamp
|
2 years ago |
|
William Grant
|
3b0d5f55e7
|
feat: added get_expiries typings
|
2 years ago |
|
William Grant
|
3cc155b9e8
|
feat: update the TTL with the snode expire result
|
2 years ago |
|
William Grant
|
32b7870e07
|
feat: make sure to use ms for the expireTimer
expireTimer on the model is in seconds so we need to convert it
|
2 years ago |
|
William Grant
|
a2185625c8
|
fix: use TTL_CONFIG in retrieve request
also some comment cleanup
|
2 years ago |
|
William Grant
|
c33eef0162
|
fix: sync messages now expire in 1on1s
fromConfig has been removed from updateExpireTimer
|
2 years ago |
|
William Grant
|
631c677a24
|
fix: trigger expiry for outgoing sync messages
|
2 years ago |
|
William Grant
|
60aac9be85
|
fix: regular messages correctly sync again
|
2 years ago |
|
William Grant
|
ec81805745
|
fix: log pipeline better
|
2 years ago |
|
William Grant
|
00ef4a47a2
|
fix: outgoing content messages can have an equal changetimestamp
|
2 years ago |
|
William Grant
|
7c6e6c981a
|
fix: make sure to note sent another message
in all remote cases
|
2 years ago |
|
William Grant
|
e8e3ba142e
|
fix: added isOutdated prop to expireUpdate
ignores duplicate setting messages
|
2 years ago |
|
William Grant
|
07097b029d
|
fix: don't send sync messages for outdated changes
|
2 years ago |
|
William Grant
|
3d8a664da9
|
fix: ignore equal lastMessageChangeTimestamps
|
2 years ago |
|
William Grant
|
50f144a8c3
|
fix: improved logging
made some progress with fixing things but other things broke
|
2 years ago |
|
William Grant
|
c24487b938
|
fix: deleteAfterSend now works in private convos again
|
2 years ago |
|
William Grant
|
a65f02a807
|
feat: use checkForExpireUpdateInContentMessage on sync messages
|
2 years ago |
|
William Grant
|
b88842b687
|
feat: tested v2 releas
made some updates to expire update generation and handling, one final fix required
|
2 years ago |
|
William Grant
|
c93315b0e7
|
fix: make sure lastDisappearingMessageChangeTimestamp is defined before comparing with convo model
|
2 years ago |