Also, are you going to remove upload_one_time_keys() from unauthenticated client service?

Rebase on top of master

Mostly looks good to me, let someone else review

https://phab.comm.dev/D8966 seems like the right approach. Closing

Make less specific than just identity service

Use debug! for read capacity

Fixed miss rename

Rebase on top of master

Rebase on top of master

Rebase on top of master

Rebase on top of master

Rebase on top of master

Rebase on top of master

Rebase on top of master

Rebase on top of master

Not sure about the specifics of authentication, but the rust looks fine.

rust LGTM, not familiar with reports though, so I would like a second opinion

Fix docker build

Rebase after conflict changes in previous diff

We don't need native as an option here.
To deliberately avoid ambiguity, I explicitly enumerated the full list of device types you should support in two places: Phabricator and Comm ("How to differentiate between different Comm devices" thread under "Services team" channel).
It's already frustrating to me that I have to micromanage to this degree. Ideally I should not have to give you explicit guidance at all, but the fact that guidance is frequently ignored means that I need to review every single one of your diffs.
This is the same problem as in D7691. There is very little that frustrates me more than feeling like the effort I put into careful, thoughtful, explicit communication is wasted and ignored.

• Remove Native
• iOS -> Ios

Add missed changes

Address feedback

Use ConnectionInitializationMessage as message name

When trying to patch this in, it got added to the previous diff. Will add @bartek suggestion to later diff

Emphasize PARTITION_KEY in comment

Address feedback. Correct async/await usage