I ended up implementing some changes here to address my above comment, and I figured it might be helpful for @kamil for me to publish them to this diff. Feel free to rework / change them as desired!

One issue I noticed while testing Farcaster sync with this diff included. We're fetching the Farcaster invites for 1-on-1 conversations, which don't support invites. The result is that it always fails with Group not found. We should only call this for group conversations.

UI looks perfect!

This is minor, but it would be good to align the content within the list, so it looks like a list. We’ve done this before somewhere in our registration flow: https://github.com/CommE2E/comm/blob/058a4e1cbe0aefc5fe453fd14bad66e8a8e6b898/native/account/registration/connect-ethereum.react.js

Landing without review as it's been reviewed by AI, tested, and I want to get a release with the fix out quickly

Landing without review as it's been reviewed by AI, tested, and I want to get a release with the fix out quickly

This seems like a lot of text, I doubt people will read it. Can we do this instead?

Classic! It probably wouldn't be very hard to start enabling React Compiler for at least some of our codebase

In D15388#423651, @tomek wrote:

If a user using this version dismisses the Farcaster connection and then connects from the profile tab, they won't see the DCs modal after the public release. This will happen because in shouldSkipConnectFarcasterAlert the alertInfo.totalAlerts will be greater than 0.