Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XIP-36: Frames Support in Review status #59

Merged
merged 4 commits into from
Jun 24, 2024
Merged

XIP-36: Frames Support in Review status #59

merged 4 commits into from
Jun 24, 2024

Conversation

jhaaaa
Copy link
Contributor

@jhaaaa jhaaaa commented May 10, 2024

Ready for Review status.

Left a few comments for review by @neekolas and @daria-github - thank you!

XIPs/xip-36-frames-support.md Outdated Show resolved Hide resolved
3. [Open Graph Proxy service](https://github.com/neekolas/og-proxy)
Still missing support for proxying requests for images. This support will be a hard requirement for launch.

Here are some specifications you might also want to explore as a part of working with these reference implementations:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See below - this is where I added the link to the Open Frames spec as suggested by Nick.

I also added a link to the Farcaster Frames spec, just to be comprehensive.


In the Farcaster model of Frames, messages are signed on a server by the app and the server makes the POST request to the Frame URL. This means the Frame app developer only sees requests from the server IP and never the client.

However, Farcaster clients, like Warpcast, download the Frame image directly. This [leaks the IP address of the viewer to the Frame developer](https://twitter.com/danfinlay/status/1752500815200399633?t=1psurRGh-JTii3AHjvUrMg). According to a reply on X, they are "[working on it](https://x.com/dwr/status/1752506807548072140?s=20)."
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know if they've fixed this?


## Reference implementations

We've developed reference implementations for all three components required to enable Frames on XMTP:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For each of the 3 items below, we call out areas that need updates. Might we have any updates to share?

@jhaaaa jhaaaa merged commit c612219 into main Jun 24, 2024
1 check passed
@jhaaaa jhaaaa deleted the add-xip-36 branch June 24, 2024 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants