frames

Frame Feature: Redirect Buttons

Buttons can send users to your webpage when clicked. You can also immediately log the user into your app using the signature packet. 

Please leave feedback in comments, feature will go live soon!

Frame Redirect Design: Redirect vs Payload 

We're considering two different approaches for implementing the redirects. Devs, which do you prefer and why?

https://warpcast.notion.site/Frame-Redirect-Response-vs-Payload-da2bb0e4212a4664ade8d38751e416f7?pvs=4

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

Response strategy seems favorable. With payload there's no room for new features (considering the URL limit) in the future and there's not much control over the action by the Frame host. Response strategy offers both flexibility on the limits and the redirect signature can be handled by the frame.

I'm guessing, with Response the client has to make the POST call to the frame and get the redirect link in response. There's an opportunity here for the client to filter and scan the link first (show a "Redirecting"...) before sending the user to the redirect link.

There wouldn't be any interaction on redirect between the user and the frame and in terms of the redirect feature, there's a limited space to fit in extra data (by both the frame and the client) on top of the redirect signature as you noted down on the URL limit of 2k bytes in case there's new data to be added in fu.

1. What control over the action is limited? In both cases you can send down a URL to send the user to, and nothing else. 

2. What new features would be prevented by URL limit?