Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction
Stephan
@stephancill
1. it's too hard for apps to request signers from users 2. it's too risky for users to give random apps full write access to their accounts (although probably not the main blocker) until this gets solved we can't really expect apps to do anything other than leech off protocol data without contributing anything back
5 replies
1 recast
21 reactions
Samuel ツ
@samuellhuber.eth
That trust is why I don’t give mine out easily or at least try to. It’s limiting though. I‘d approve one off casts though so the Auth addresses FIP will likely enable that so I add my wallet as Auth address and then can sign off on single casts to be posted via a mini app or something else
1 reply
0 recast
4 reactions
Tony D’Addeo
@deodad
similar challenge to push to wallet vs session keys push to wallet is so much easier to reason about seems hard to dislodge, especially in an fully integrated experience like Warpcast my guess it has staying power and app keys remain more or less limited to sophisticated use cases, even if it's easier to setup and with more granular permissions (though ofc these would go a long way)
1 reply
0 recast
4 reactions
df
@df
unclear why you can't request a signature to create a single cast via the miniapp sdk - just a simple single permission
1 reply
0 recast
3 reactions
christopher
@christopher
#2 is stated versus revealed. Most folks haven’t really cared because they treat it like a password (which is very insightful, all told).
1 reply
0 recast
0 reaction
Koolkheart
@koolkheart.eth
You nailed it. The signer UX is so broken that even devs feel friction testing their own apps. Needs a smoother delegation model
0 reply
0 recast
0 reaction
