Request, @v @deodad 

FIP-2 replies to miniapps. Farcaster knows very well how to present, embed, etc, a miniapp, why not allow us (i.e. make them usable) to use FIP-2 with miniapps?

Example: https://farcaster.xyz/fc1/0x14accf3f
which has parentUrl set to https://blog.vrypan.net

In my case, I would like to use it for my blog comments. But it could also be a great way to comment/leave feedback about miniapps.

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

@farcaster dev / dad / books, cooks, ski, code ~ there are many things of which a wise man might wish to be ignorant

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

i like it

where would these get surfaced?

Ideally the app would set a directive for this not unlike announcing to a host that it requires a certain chain. Or maybe robots.txt is a better framing. Don’t use this app’s casts & reactions but use its Links types. Read & write casts & reactions to this app’s namespace but don’t write replies. Etc

Actually, @deodad I think that the /url/<url> page would be an amazing feature for Farcaster. The promise of FIP-2: like, comment on any URL.

So, I would go to `farcaster.xyz/url/https%3A%2F%2Fdev.to%2Fbuntine%2Fthe-balanced-ternary-machines-of-soviet-russia`  and I will see the OG representation of the url, and I will be able to like, comment. And you will see in your feed that I commented on it.

And it's the easiest way (just contract the URL) to add interactivity to any page on the web.

Ideally, there should be a `farcaster.xyz/url/urlized_url>` endpoint that renders FIP2 and shows reactions and replies.

I can think of two use cases, but I'm sure there will be more:

1. Link from miniapp store, where you can see the reviews/comments about the app.
2. Under every post in my blog, I will have a "comment" link that will link users to comment on the post URL (my blog is a miniapp).