Greg
@greg
Farcaster signers should have scoped permissions. I’m hesitant to use non-Warpcast apps today because of this
6 replies
2 recasts
13 reactions
Greg
@greg
I’ve actively avoided the Farcaster integration in 2 apps now because I just wanted to be able to like/reply to casts but didn’t want to give the devs the ability to wipe my entire profile
0 reply
0 recast
1 reaction
blobs
@blobs
if you’re concerned with @blobs feel free to delete your @blobs signer after linking; we don’t store your signer at this time … just to link your FID for fren suggestions, ecosystem integrations and figuring out your eth address for NFT deliveries 🙂
1 reply
0 recast
0 reaction
timdaub 🥝
@timdaub.eth
They should also allow you to select where you want to send the delegation message to. Right now Warpcast is like a Metamask where Ethereum mainnet is hard coded. At Kiwi, we‘d be able to deliver „Sign in with FC“ if the RPC endpoint was selectable
1 reply
0 recast
0 reaction
Zach
@zachterrell
https://i.imgur.com/pFFE9hv.jpg
1 reply
0 recast
8 reactions
Dan Romero
@dwr.eth
cc @v who I'm sure has thoughts on this. My smooth brain POV is it's probably possible but would require a significant change / additional complexity to Hubs model. Opportunity for an indpt company that does a Warpcast-style API + Hubs and allows you to create the permissions off-protocol.
1 reply
0 recast
2 reactions
Boris Mann
@boris
This is needed generally. This is the model for UCAN And delegating object capabilities based on keys / DIDs. SpruceIDs ReCap is more onchain and also aiming for UCAN compat. @depatchedmode is talking permissions in the Secure Design WG right now.
0 reply
0 recast
1 reaction
