Handle history archive magnetlink messages

This introduces the ability for status notes to handle community history archive magnetlinks. To make this work, a few things are needed: 1. A new database table has been introduced to store message archive hashes. This is necessary so status nodes can determine whether or not they need to download a certain archive 2. The messenger's `handleRetrievedMessages()` has been exteded to take magnetlink messages into account 3. New APIs were added to download torrent data given a magnetlink and also to extract messages from downloaded archives, which are then later fed to `handleRetrievedMessages` Closes #2568
status-im · Mar 23, 2022 · e8e7cbe · e8e7cbe
1 parent 2bf79e9
commit e8e7cbe
Show file tree

Hide file tree

Showing 11 changed files with 357 additions and 48 deletions.
diff --git a/appdatabase/migrations/bindata.go b/appdatabase/migrations/bindata.go
diff --git a/appdatabase/migrations/sql/1647957841_add_community_message_archive_hashes_table.up.sql b/appdatabase/migrations/sql/1647957841_add_community_message_archive_hashes_table.up.sql
@@ -0,0 +1,5 @@
+CREATE TABLE community_message_archive_hashes (
+  community_id TEXT NOT NULL,
+  hash TEXT PRIMARY KEY NOT NULL
+);
+