Change Details

At the moment, the data in the synced metadata table store is not properly synced + shared across different clients. This has two consequences: 1. the web client will not have an fid. 2. If the user logs out on `native` after connecting to farcaster their `fid` will be lost because the sqlite client db will get cleared We have an identity RPC called `findUserIdentities` where we can pass in the current user id and check if they have a farcaster id in the identity service and store. If the user has an fid persisted in the identity service we can grab it from there and also store it in the synced metadata table store through `handleCurrentUserFID`. A subsequent diff will handle checking if the user fid is still valid and if it isn't handle unlinking/removing the fid Depends on D12568

At the moment, the data in the synced metadata table store is not properly synced + shared across different clients. This has two consequences: 1. the web client will not have an fid. 2. If the user logs out on `native` after connecting to farcaster their `fid` will be lost because the sqlite client db will get cleared We have an identity RPC called `findUserIdentities` where we can pass in the current user id and check if they have a farcaster id in the identity service and store. If the user has an fid persisted in the identity service we can grab it from there and also store it in the synced metadata table store through `handleCurrentUserFID`. A subsequent diff will handle checking if the user fid is still valid and if it isn't handle unlinking/removing the fid Depends on D12683

At the moment, the data in the synced metadata table store is not properly synced + shared across different clients. This has two consequences: 1. the web client will not have an fid. 2. If the user logs out on `native` after connecting to farcaster their `fid` will be lost because the sqlite client db will get cleared We have an identity RPC called `findUserIdentities` where we can pass in the current user id and check if they have a farcaster id in the identity service and store. If the user has an fid persisted in the identity service we can grab it from there and also store it in the synced metadata table store through `handleCurrentUserFID`. A subsequent diff will handle checking if the user fid is still valid and if it isn't handle unlinking/removing the fid Depends on D12568683