Content
@
https://warpcast.com/~/channel/miniapps
0 reply
0 recast
0 reaction
Ashoat
@ashoat.eth
I'm working on a proposal for a "capabilities" API that allows Mini Apps to declare which capabilities/chains they require, as well as querying at runtime to discover which capabilities/chains are supported. Would appreciate any input! https://github.com/farcasterxyz/miniapps/discussions/256
5 replies
10 recasts
39 reactions
Samuel ツ
@samuellhuber.eth
cc @darrylyeo who also pitched in on https://github.com/farcasterxyz/miniapps/discussions/240#discussioncomment-13108720
0 reply
0 recast
6 reactions
Linda Xie
@linda
cc @rish @manan
1 reply
0 recast
5 reactions
MJC
@mjc716
i think you guys should highly encourage a minimum standard for mini-app clients because this sounds like it could get very messy for devs you don't want to have much custom logic for different clients
1 reply
0 recast
4 reactions
KMac
@kmacb.eth
Can we move some of this to use snapchain as a registry for hosts & apps? Even better of we start thinking of them all as apps. Peers leveraging a globally consistent shared state. There seems to be a lot of host announce something app decides what to do with that info & app announces something & host decides... At least & please consider moving the manifests onNode have that & verifications crack open the need to THINK more about flexible profile attributes & non-social message types, links & reactions. Huge opportunity to unlock devs. App graph. There’s something bigger to be had here. [insert some saying about being off one nautical mile at the beginning] Keep going! 💜
0 reply
0 recast
0 reaction
Monica Talan 🌐 🍄🎭
@monitalan
Cc @chaps
0 reply
0 recast
0 reaction
