I just want us to have fun | Cofounder @ Resolve (YC) - spatial tech for construction. FC tinkering: @livecaster @harmonybot | Ask me about /f1 /vr /orange-dao

I am so freaking bullish on just building things and letting that speak for itself. 

Founder, designer, & product guy at /basepaint
Prev: Eigenlayer, ConsenSys, Gitcoin, Arweave, Protocol Labs, & MIT DCI

litewrite.vercel.app , lil thing I've been noodling on.

Transdisciplinary artist, working with traditional and digital painting, 2D animation, 3D and music // she/her — https://thehug.xyz/artists/qabqabqab

if you want, you can guerrilla market it by creating your own managed signer on neynar that points to your app's fid when you're ready.

gonna ask a buncha dumb questions
1. docs to managed signer?
2. is this on the trial plan bc thats all I can afford rn
3. why would my app have a FID?

1. https://docs.neynar.com/docs/integrate-managed-signers

2. signers aren't free but they are cheap: https://dev.neynar.com/pricing#section_api_rest_signer

3. Anything that writes to the farcaster protocol must have a fid and therefore a signer. It's like have a keypair on a blockchain except it moves the key management onus from users to devs, since devs manage signers for their apps on behalf of users and signers can be rotated and changed without losing or changing fids.

So essentially, because you are managing protocol interactions on behalf of users with your signers, the signer resolves to the fid of your app, even if the user is initiating the interaction. It's why your post is showing up as "casted from neynar", because you used a neynar-managed key to cast from your new client.