I think you should rename the generic backup_message to siwe_backup_message

Two questions:

1. Could you explain why we need backupID? The message to sign seems generic and wondering if we need a separate file for each backupID
2. Is there an easy way to somehow unify getSIWEBackupMessagePath with getBackupUserKeysFilePath which is basically doing the same?

lint

rebase before landing

use olmSessionErrors instead of hardcoded string

move olmSessionErrors from errors.js to olm-utils.js

rebase

introduce setter & getter

rebase

In D11577#334170, @marcin wrote:

In D11577#333862, @ashoat wrote:

We should implement it for notifs while working on DMs - now there is no need to I guess.

Is there a task for this?

I think it is https://linear.app/comm/issue/ENG-7658/add-olm-session-versioning-for-notifs - is that correct @kamil ?

rename to add_version_column_to_olm_persist_sessions_table

In D11577#333755, @marcin wrote:

Not familiar with this project so letting others review, persistWhitelist looks good

Could you extend the test plan to

1. Add an unknown user to the friend list
2. Block user
3. Using two clients change the avatar on one and check if it gets synced on the other

Refreshing app multiple time between steps

Looks good

LGTM but leaving final review to native speaker

In D11481#331389, @marcin wrote:

Accepting but I am of strong opinion that it would be better to create two new structs: NonSyncedKeyserverInfo and SyncedKeyserverInfo that would look exactly the same as original KeyserverInfo. In SQLiteQueryExecutor methods we would just create instances of each class and could rely on simple SQL queries without named parameters. The code would be easier to understand and maintain. It would be two small classes doing simple logic instead of one bigger doing complex logic.