Zach
@zherring
I am so freaking bullish on just building things and letting that speak for itself.
2 replies
2 recasts
19 reactions
Zach
@zherring
Neat.
1 reply
0 recast
1 reaction
qabqabqab
@qabqabqab
wait what is this? 👀
1 reply
0 recast
1 reaction
Zach
@zherring
litewrite.vercel.app , lil thing I've been noodling on.
2 replies
0 recast
5 reactions
Topocount
@topocount.eth
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.
2 replies
0 recast
2 reactions
Zach
@zherring
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 reply
0 recast
3 reactions
Topocount
@topocount.eth
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.
1 reply
0 recast
0 reaction
Topocount
@topocount.eth
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.
0 reply
0 recast
0 reaction
