Content
@
0 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
Since FC hub data is public, what's the benefit of using SIWF over connecting with a wallet and associating a FC account (like @paragraph @bracketgame et al), and just pulling the social graph / content as needed? Especially since connecting a wallet is more decentralized than doing OAuth facilitated by Warpcast?
9 replies
4 recasts
24 reactions
Matthew
@matthew
it's one tap for siwf vs two with siwe, assuming all users have warpcast (which mine do, at least right now)
2 replies
0 recast
5 reactions
androidsixteen
@androidsixteen.eth
For your use case, it makes more sense - you’re not targeting any audiences outside of Warpcast (at least initially) What about for builders / apps targeting a broader crypto audience? Or even if they are focused on Farcaster, the optionality seems useful since FC isn’t huge yet
2 replies
0 recast
0 reaction
agusti 🐘
@bleu.eth
for builders an interseting compromise is siwn (@neynar) so you can reuse previously authorized signers by 35k userbase neynar already has this make it 1 step if they're already preauthed in any neynar signer based app
1 reply
0 recast
2 reactions
agusti 🐘
@bleu.eth
im considering using siwn over siwp or siwe/wallet
1 reply
0 recast
1 reaction
Matthew
@matthew
i may switch over given that there’s row level permissions now in SIWN. wasn’t using it before bc eventcaster doesn’t cast on your behalf, so i didn’t want to scare off users by asking for more permissions than needed.
0 reply
0 recast
2 reactions
