Sorry, you're absolutely right... that was my mistake, I mixed up FUTURE_CODE_VERSION and NEXT_CODE_VERSION

In D13888#388166, @ashoat wrote:

Hmmmm this doesn't look right... the file on the left doesn't seem to be master

There's now an increasingly long list of "dangling" functions/types that can be removed:

Rebase, add invariants for encrypted uploads, remove more dead code: legacy calls

Hmmmm this doesn't look right... the file on the left doesn't seem to be master

Use version 389 as minimal

• Made primary device non-clickable
• Added pencil icons to editable items
• Refactored isThisDevice
• Made type readonly

Remove padding

Neat ideas, I came up with something like this (the first item is not clickable):

Thanks for explaining and sharing the details & logs!

I talked with @tomek, and we concluded that I had previously done the test plan wrong, and the migration didn't actually run. In short, I was logging in with state version 85 from the beginning.

Rename

Rebase and rename

Make notificationsCreationData optional

I did not do any testing. @barthap will need to test this before landing, thoroughly this time.

1. Split out legacyUnshimClientDB for existing usages
2. Introduce new unshimClientDB
3. Do the same for web

First, give this comment a read.

Reverted this diff because blob-hosted multimedia in thin threads will get shimmed by the keyserver to recent mobile clients.

minimal Cargo.lock update

add argon2 to root Cargo.toml

realize there's Rust code so @ashoat isn't a good reviewer