Andy Balaam

Gack, github tasklist overwrote the whole issue with an old version. I tried to fix it - sorry if I did it wrong

Hi @Valodim, thanks for the message - I can see lots of people are still affected by this. You can follow our progress somewhat by looking at the tasks closed...

I'd also like to say again how sorry we are for the pain this is causing to lots of people. We are all heavy users of Element Web, and have...

Plan: * Change "needs_backup" field into "most_recent_backup_to_include_this" so we don't need to modify all records when the current backup version changes. * Reduce the size of the values in inbound_group_sessions2...

Previous plan doesn't work without a migration because we can't efficiently query for records that **don't** have a matching `most_recent...` field. Next idea: assign each backup version an order number,...

Not blocking Element R release because if we do https://github.com/element-hq/element-web/issues/26930 we will be on-par with legacy crypto. (But we should still do this later.)

To speed up key backup resets: * [ ] Store current backup order number and ID in Indexed DB, probably in the `core` store, or in `backup_keys`. Default it to...

I just had a conversation with @poljar and @richvdh about how we can implement this. Here are my notes from our conversation: * Modify `inbound_group_sessions_for_backup` and `mark_inbound_group_sessions_as_backed_up` so they take...

Had a further conversation with @richvdh today where we realised we can simplify this a bit, but still make use of the `backed_up_to` field we added in the last schema...

## Code ### DB migration Create a store called `backup_reset` with no index. ### inbound_group_sessions_for_backup Check inside the `backup_reset` store for a `backup_reset` property. If it does not exist or...