I wonder if I would get banned for just reposting things Balaji said on X? Charge sheet by @geesmike
webthe3rd.eth
SNAPSTART: Farcaster in three commands Submission links: [1] webthethird.github.io/snapstart/ [2] github.com/webthethird/snapstart [3] farcaster.xyz/ivc/0x05315d8a

Run your own Farcaster client
A Snapchain read node you own, and a client that reads from it, in three commands. No API keys, no hosted provider.
GitHub - webthethird/snapstart: Run your own Farcaster read node and a client that talks to it, in three commands. No API keys.
Run your own Farcaster read node and a client that talks to it, in three commands. No API keys. - webthethird/snapstart
I just completed @ivc's quick and easy submission to the Farcaster client bounty:
@borodutch I'd love to try switching to Quilcast, but I'm concerned about my Farcaster recovery phrase being stored unencrypted in the browser storage. I just opened an issue on Github, and would be happy to put together a PR if you are open to this change.
@farcaster what's the status of this proposal to add direct casts to the protocol? Many clients would be good for the ecosystem, but right now DCs are a client-level feature, and they should be portable. A new client should be capable of restoring DC access to anybody who opts out of the @ns client.
