Switch clients.
Keep your FID.
Client portability has two parts: shared Farcaster protocol records and client-specific presentation. An app's login session is not itself a protocol identity.
What is portable?
| Shared protocol | App-specific experience |
|---|---|
| FID, custody account and authorized app keys | Cookies, app sessions and private drafts |
| Canonical casts and replies | Feed ranking and suggested content |
| Follow links and signed reactions | UI preferences, internal bookmarks |
| Onchain account state | Third-party notifications and service APIs |
Access to the records still depends on a compatible protocol reader or indexer. Not every client exposes every feature.
Switching sequence
Changing clients should not require a new FID. Use separate authorized app keys and review permissions when leaving old applications.
Including or excluding posts by originating client
Client-origin filtering requires trustworthy attribution. A correct implementation must validate signer provenance and a trustworthy mapping from app key to client. Arbitrary text labels and the hostname of the reader are not proof of origin.
Still a planned feature
Client-origin filtering is not yet certified as complete in Genycaster. Until an audited mapping exists, mark uncertain origins as unknown rather than claiming an accurate filter.
Account and data safety
Keep account recovery secrets outside website forms, logs and node-provider requests. Authentication, reading protocol data and authorizing a write client are separate security boundaries.
Learn more: provider routing, local-first architecture and getting started.