Farcaster Devs

New proposal to allow Mini Apps to set a path and query params to be used when clients share the Mini App URL.

New proposal to allow Mini Apps to set a path and query params to be used when clients share the Mini App URL.

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

building wyat.live, bondes.xyz and fiids.xyz

The open web is dead, long live the open web. ⌐◨-◨

Building /warpcast and /farcaster

— gabrielayuso.com

cc: @alvesjtiago.eth since you requested this IIRC

Nice one! Just make it feel a little more JavaScript native 😄

/frontend dev (HTML/CSS)・founder/decentralized data wrangler /blockhead・contributor /ethglobal /walletbeat・hackathon bounty hunter・music maker・dropout・nomad・25

Thx for the suggestion. I'm not very familiar with any of that lol.

Although the ShareState or ShareUrl type is likely going to be inferred from a zod schema so we have runtime validation.

Nice one! Just make it feel a little more JavaScript native 😄 

https://github.com/farcasterxyz/miniapps/discussions/227#discussioncomment-13056850

Not sure if I understand your question since there is no built-in referral system.

This proposal makes it easier for mini apps to build their own referral links by telling the host (i.e. Warpcast) the query params they want to add to the mini app links. Without this, the host would just use the homeURL from the mini app manifest.

Does it affect the referral link?
How to handle it for the referral link system?

i like it,

i’m not sure i’ll need the subpath, query params might be enough

but yeah i see how for some use cases the subpath might be handy

I think this is great. Passing params through the URL allows compose cast have fun use cases.