Question for fc devs:

Anytime we want to use any farcaster client that’s not warpcast, we have to sign a transaction to authorize that client to cast on our behalf and/or edit our profile. 

How come warpcast doesn’t need to ask permission?

customer support @supercast

trying to sound smart /doingnumbers

Cohost /gmfarcaster livestream Farcaster news show 🎙️💬 Founder Tenger Ways, bringing joy into work with DevOps practices 🤗 mom x 3 💗

It’s not a requirement. It’s just how people have it designed today for practicality / speed of implementation. cc @woj.eth

it is a requirement, unless i don't understand what we are talking about

If you have a signer you don’t need SIWF. 

Auth != write access

You could onboard a user, set up signer and auth in the future with email.

ah yes but @adrienne is specifically asking about the permission to cast or edit profile

supercast (which adrienne recently onboarded on) asks for a signer approval only after you attempt writing to the protocol

💻 building /hyperclient && @atlas && @gif composer action (check bio for details) | 👑 support me and @gif project by subbing to https://hypersub.xyz/s/gif

cc @0xconca.eth remember you were wondering about this when we set up  @hyperclient.eth (the delayed signer approval)

best farcaster developers build on neynar.com | /neynar

Yeah, the concept is clear but i still wonder how @woj.eth does it from a practical pov using @neynar 😁