Shower Thoughts

App inception is real & we should embrace it. More & flexible context-containers pls.

What if we did something like this:

- Frame Navigator API : allow seamless navigation between frames inside a session.
- Ephemeral frame session / state / storage: scoped to the session onHub or node, not onchain, fast & lightweight.
- Agent-readable context surface:  structured session data agents can use to navigate, compose, negotiate on the user’s behalf.

Frames would stop being just a lowly embed & become Peers in the Farcaster network. App to App. Winning together. 

They’d become composable markets where users & agents cooperate , transact, & build new experiences fluidly all onHub/node. 

[turns off hot water first & hopes wet laptop continue to function]

[artist and dev] <>building things like /hamsters /rewardr cooking THE BOLE and decorating THE WARPROOM. chilling in tub often. doing things I like</>

Ethereum builder & people connector. Juicebox, Revnet, Defifa & Footy App

hamst.art $hamster /hamster 
martinvr.eth 
deploy.degen.eth

Yeah your stuff def motivating & well brave 😆

Auth keys will help & nice to read those are assumed to be happening

The client server thinking is so pervasive in the design choices to date I wonder if we will ever see app to app coordination. Let’s nudge, bark, push with POCs & see if we can Shepard this into existence

Been doing this with @dosir but relying on a custom implementation which they broke recently with stricter context rules

Seems like an obvious winner to me the implementation details aside

at trust wallet via sequence. pimlico. poap. polygon. metamask. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia. linktr.ee/alexanderchopan

have u ever been down the ink and switch rabbit hole?