Which warpcast dev is looking at what I'm testing at regarding Frames 👀

I see you

software engineer & cto - building /sukuri - foss advocate - creator of /frame-token - maxbridgland.twitter

If it wasn't a warpcast dev, then there's a concern here because I just generated a fresh ngrok link, never shared with anybody, and only tested through the Frame viewer on Warpcast itself.

@dwr.eth

I'm eth newbie..just learning
(working on @farcaster)

terminally.online

If you used our frame validator that means we attempted to make a request to parse your page headers so we can show the frame. Its not a local tool?

I was testing my website's frame using an ngrok link and the Warpcast Frame validator. After submitting some requests, I noticed somebody else (who wasn't me) somehow got the ngrok link and started looking around the site.

I'm not sure how this is possible given I had just generated a fresh ngrok link. I attempted to make a new ngrok link, and waited for a couple minutes to try and test again. As soon as I put the new ngrok link in, somebody else was accessing the link.

I can't think of any way this would be possible unless the warpcast proxy can be read by a third party or a warpcast developer was reading logs and visited the site. Seems like it might be an issue.