Farcaster Devs

How are cast actions doing?

What's the plan with them? Will the POST Message -> Message stay around? 

When will they open v2 Frames? If so is there a POST message before or predefined link?

Will we get Cast Actions on direct messages?

am currently working through updating my map of all Farcaster legos and cast actions have no roadmap I am aware of.


I'm eth newbie..just learning
(working on @farcaster)

terminally.online

Building @warpcast and @farcaster, new dad, like making food

Farcaster Product Studio @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

cc @dwr.eth @horsefacts.eth @deodad I know frames v2 is high prio right now, though is there any existing mental map on  cast actions?

My personal roadmap for dev legos would be
- get Frames V2 stable
- add cast actions to direct messages
- add frame V2 support to cast actions to open them

No more "cast actions," "composer actions," "mini apps," "action deep links," etc. Everything will just be a frame, with different ways to launch it.

Cast actions will become frames that define a "cast" trigger. Composer actions will become frames that define a "composer" trigger. (see docs below)

Current cast actions will probably never open v2 frames. Migration plan is TBD, we'll continue to support this stuff if people are actively using it, but really want to encourage migration to v2.

No more "cast actions," "composer actions," "mini apps," "action deep links," etc. Everything will just be a frame, with different ways to launch it.

Cast actions will become frames that define a "cast" trigger. Composer actions will become frames that define a "composer" trigger. (see docs below)

Current cast actions will probably never open v2 frames. Migration plan is TBD, we'll continue to support this stuff if people are actively using it, but really want to encourage migration to v2.

https://docs.farcaster.xyz/developers/frames/v2/spec#feature-triggers

yeah but v2 frames means no context menu on casts that send to backend? is that really going away in Warpcast?

I got the it's all frames (v2) though having that context menu for programmability is powerful. The longtail of customized experience for business processes, specific communities etc is so great with it. Not every one button press needs to be forced into opening a frame

headless frames? that's a nice naming!

the headless setup I don't envision to have high high usage numbers on one endpoint but high value.

it's low volume, high value

take @0xmelanin moderating supercast channel and direct messages.

If there's a headless frame to tag support messages into one combined issue that one can use to get back to all users having the issue once it's closed that is 
1) great support experience
2) great dev experience to rank high priority issues by # users asking

Another example is  adding a user to a marketing list which could integrate with what @percs and others are building.

These will have low # users but save thousands of dollars in time

So headless frames everywhere would be king.

i'd be sad if that programmability went away or forced someone into a webapp (frame v2) that then just calls the backend

Yeah, if you have suggestions here definitely open to them in the spec. "One shot" actions from frames v2 are still not really defined and this would be similar. Probably an attribute on the trigger that defines it as "headless." We now have a webhook setup on the frame manifest for notifications, maybe these are a new event type that gets sent there.

But usage is pretty low in existing actions. Would have to check the stats to get an exact number, but the vast majority of existing cast actions are just used as shortcuts to open frames.

I agree with that.

headless frame horsefacts proposed works well for that. I am a fan of that rebrand to just have everything be Frames (and adjusted the weekly copy pasta as per last week :D )

I think it's important as part of v2 to simplify everything to into "frame". (Per your weekly cast / composer actions cast.)