Auto-reTOFU checklist
Here are some cases where I think #277 messages should be used, and obviously no messages shall be lost.
Allegedly there might be some unknowns in how to merge an e164 and uuid session when a user buys a new phone, which should be figured out.
-
Sending to someone with a new phone -
When they used their PIN to recover their account (real re-TOFU) -
When they did not use their PIN to recover their account (new account with same number)
-
-
Receiving from someone with a new phone -
Sending to a group with a member with a new phone -
Receiving from someone with a new phone in a group -
Sending to someone new (i.e. start new session) related to #237 -
Receiving from someone new (i.e. having a new session started)
I can't remember the exact details of how go-Whisperfish noted these in the session view, it probably didn't at all. Sending to a group with a member with a new phone did bring up the accept/cancel qml page with the new identity key.
Would it be super hard to tie in the megaphone table so that e.g. "send to a group with a member with a new phone" would record that identity update, and then it'd also be visible in the chat session with the recipient?
Just a piece of mind checklist because messages have been lost for me and many others.