Michael Pfister
@pfista
would love if warpcast and other clients chose to display which signer a cast came from below a cast
4 replies
0 recast
24 reactions
Michael Pfister
@pfista
could lead to discoverability of new apps worth checking out hmm should we support this in buoy?
5 replies
0 recast
22 reactions
patxol ð· anser.social
@patxol.eth
It would not give you much information for apps that use @neynar signers.
1 reply
0 recast
1 reaction
Michael Pfister
@pfista
Thoughts @rish @manan? Do yall expose more info about the app through the api
1 reply
0 recast
1 reaction
rish
@rish
you can use neynar signers in many different ways - there are many apps on the protocol using neynar signers underneath while branding it as their own - supercast, kiosk, buttrfly, etc. This data can be found at the protocol level where protocol will show the signer being from supercast. then there are apps that use SIWN because it has a built in frontend - recaster, phaver, etc. These show up on the protocol as Neynar signers but we can expose in our API what the app behind the scenes are. More data on the different ways to manage signers here: https://docs.neynar.com/docs/which-signer-should-you-use-and-why
2 replies
0 recast
4 reactions
patxol ð· anser.social
@patxol.eth
And some even use a mix :-). Depending on how you wish to connect your Farcaster account to @anser-social.eth , you would either have a SIWN signer or an Anser branded one (for sign in with custody wallet)
0 reply
0 recast
1 reaction
Michael Pfister
@pfista
Thanks!
0 reply
0 recast
1 reaction
