wrote up a for Share Extensions, a Mini Apps ecosystem successor to cast actions

if you have substantive technical / product feedback please reply to the GH discussion linked below

for +1 or hell yeas please use Farcaster comments or reactions in GH

wrote up a for Share Extensions, a Mini Apps ecosystem successor to cast actions

if you have substantive technical / product feedback please reply to the GH discussion linked below

for +1 or hell yeas please use Farcaster comments or reactions in GH

https://github.com/farcasterxyz/miniapps/discussions/158

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

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

immediate concern I have is that unless we explicitly block actions that aren't specified like in mobile dev these will quickly get out of date / devs just wont specify

and explicit blocking seems like a huge piece of friction

what do we get from this?

+1 to this! wanted to quickly call out one more idea: in this FIP you mentioned that deeplink URLs could be specified in a mini app's manifest.json -- curious if you think it'd be a good idea to similarly have the manifest.json list the sdk functions a mini app is planning to use, kinda like how with an iPhone app you toggle the permissions your app will be requesting

^ from the frame host perspective, something like that would be very helpful for handling cases where there are issues with a particular sdk action

Mini apps will eat the internet | Latest drop: /clankermon | Building : /large /fctrivia /miniapps /flappycaster /jeeves /source @degentip @playsource /jump

unlikely but maybe that'll be the reference implementation :)

My only question 

Are you going to update the linear cast action 😂