would love if warpcast and other clients chose to display which signer a cast came from below a cast

𝓵𝓲𝓿𝓲𝓷𝓰 𝓽𝓱𝓮 𝓮𝓷𝓭𝓵𝓮𝓼𝓼 𝓼𝓾𝓶𝓶𝓮𝓻 • building @buoy 🛟 • pfista.com

Nomad Rural LLG, Western Province, Papua New Guinea

could lead to discoverability of new apps worth checking out

hmm should we support this in buoy?

best farcaster developers build on neynar.com | /neynar

It would not give you much information for apps that use @neynar  signers.

🪐 Building @neynar, join us in /neynar

working @ /neynar   🪐  casting @ /rish

building /anser https://anser.social | prev. Ledger

Thoughts @rish @manan? Do yall expose more info about the app through the api

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:

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