Content
@
0 reply
0 recast
0 reaction
horsefacts
@horsefacts.eth
Handling all Frame redirects by returning 302s is a bit of a pain. We are considering simplifying the design. If you have feedback or suggestions on simplifying redirects, I'd love to hear them! One obvious addition is a simple "external link" button with no server round trip. What else could be better?
7 replies
2 recasts
38 reactions
Varun Srinivasan
@v
cc @w1nt3r
1 reply
0 recast
3 reactions
Zinger โ
@zinger
One of my concerns when Varun originally mentioned that as an alternative was that it can get stale, especially for stateful frames The nice thing with the 302 (while it does feel a bit cumbersome) is that you can add validation and logic thatโs executed when the action is taken vs. when the frame is rendered
2 replies
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
I still don't understand why the post_redirect does not happen in the browser, and you need an intermediate step. (Isn't there a browser equiv of curl -X POST?)
2 replies
0 recast
0 reaction
Adalarasu
@adalarasu
Multiple frames in a single HTML document, each display based on button clicked. Saves a lot of roundtrips and latency.
2 replies
0 recast
3 reactions
conca ๐ฉ๐ป
@0xconca.eth
is this still a proposal? https://warpcast.notion.site/Frames-External-Links-Public-60c9900cffae4e2fb1b6aae3d4601c15 What's the correct way of redirecting the user to an external link atm? Struggling at figuring it out from the docs ๐ Thanks!!
1 reply
0 recast
0 reaction
Paul Cowgill
@paulcowgill
The external link button is a great option!
0 reply
0 recast
2 reactions
markus - ethOS - e/acc-d
@markus
Simple external link would enable in-feed tx signing on ethOS, would love to see it
1 reply
0 recast
1 reaction
