when the frame sdk is(hopefully) updated to allow for signer access/creation, there will be some cool unlocks for tap videos:
- like/recast/comment on a video directly from the frame
- upload/create new videos directly from the frame

hoping these will be possible to implement soon!!

engineer @base | /farhack /tap /cortex | dylansteck.com

What does like/recast/comment look at the protocol level? Does each video have it's own cast I can react to, or is it FIP-2?

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

right now i just mean reacting to the cast the video is embedded in(just like any other reaction, not any FIP-2 stuff although there could be some fun stuff to explore there)

the main hurdle i had was making a signer in a v2 frame but i *think* i have a solid workaround for now

Imo, these should be social actions offered by the sdk. The frame is rendered inside a client that already has a signer, the frame should be able to tell the client the user wants to react to a cast and do it (maybe with an extra confirmation step).

Having your own signer opens a lot of possibilities. Personally, the way signers work today, the implications and the friction required to revoke one, I'm very reluctant to casually approve new ones.

But `sdk.action.like(cast)` seems like a reasonable thing to have. Frames could abuse it, and trigger 100 likes, that's why the client should ask for confirmation, and I think it'd be pretty safe and simple.

especially just for reacting i agree, there certainly shouldn't be access to the warpcast signer though

i think a good solution here is a developer can either take *very fine grained* actions with the existing signer if the user consents, or the developer is able to have the user create a brand new signer (and both should happen through the frame sdk)