Improve auto-rage shake

[BillCarsonFr]

• [x] Add labels for sender / recipient uisi-sender / uisi-recipient
  • [x] Web
  • [x] Android
• [x] Use a new app when sending rageshake => https://github.com/matrix-org/z-uisi-rageshakes (waiting for final app name)
  • [x] Web
  • [x] Android
• [ ] Only report UISI from incremental sync?
  • [x] Investigate on web
• [ ] Grace period or wait for catchup sync? For when we get the m.room_key in the catchup sync after the message. Ideally we would like to get a rageshake when the key was forwarded and not just initialy shared.
  • [x] Web
  • [ ] Android

DEv issues

• Android https://github.com/vector-im/element-android/issues/5021

[BillCarsonFr]

Also as we are now reporting to the same repo, we could also add a platform label to the issue android / web / ios / desktop ? WDYT @duxovni

[emmaburton1]

Does this work have in-scope the option to send an auto-rageshake if keybackup is either not enabled or not working?

[duxovni]

If key backup issues cause you to be unable to decrypt messages, then it'll rageshake at that point; is that the functionality you're looking for @emmaburton1 ?

[emmaburton1]

Yes, that's it.

[duxovni]

Filed matrix-org/matrix-react-sdk#7650 to address the remaining improvements on the web side of things. We've now got approximate checking for initial vs incremental sync, and a 5-second grace period for decryption failures to resolve before rageshaking.

[benparsons]

There is also a need to auto-rageshake in the condition where the keybackup fails or is not loaded: https://element-io.atlassian.net/browse/PSE-327

[benparsons]

[richvdh]

@BillCarsonFr is there anything left to do here?