Fix some issues with pinned messages

There were a couple of issues on how we handle pinned messages: 1) Clock of the message was only checked when saving, meaning that the client would receive potentially updates that were not to be processed. 2) We relied on the client to generate a notification for a pinned message by sending a normal message through the wire. This PR changes the behavior so that the notification is generated locally, either on response to a network event or client event. 3) When deleting a message, we pull all the replies/pinned notifications and send them over to the client so they know that those messages needs updating.
status-im · Apr 20, 2023 · 5af3563 · 5af3563
1 parent 272173c
commit 5af3563
Show file tree

Hide file tree

Showing 27 changed files with 801 additions and 510 deletions.
diff --git a/appdatabase/migrations/bindata.go b/appdatabase/migrations/bindata.go
diff --git a/appdatabase/migrationsprevnodecfg/bindata.go b/appdatabase/migrationsprevnodecfg/bindata.go
diff --git a/mailserver/migrations/bindata.go b/mailserver/migrations/bindata.go
diff --git a/multiaccounts/migrations/bindata.go b/multiaccounts/migrations/bindata.go
diff --git a/protocol/anonmetrics/migrations/migrations.go b/protocol/anonmetrics/migrations/migrations.go
diff --git a/protocol/common/pin_message.go b/protocol/common/pin_message.go
@@ -31,6 +31,8 @@ type PinMessage struct {
 	Identicon string `json:"identicon"`
 	// Random 3 words name
 	Alias string `json:"alias"`
+
+	Message *PinnedMessage `json:"pinnedMessage"`
 }
 
 type PinnedMessage struct {