@v, any possibility of implementing FIP-202 in the near future?

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

@v, any possibility of implementing FIP-202 in the near future?

https://github.com/farcasterxyz/protocol/discussions/202

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

> Being able to translate a web URL to the corresponding Farcaster resource in an easy and standardized way, could make easier the introduction of a Farcaster URI Specification (farcaster://) in the future.

can you elaborate on how you see this working?

Farcaster-DevCall-250313.mp4
Farcaster Dev Call: Mar 13, 2025

[with lemon3]

Technically I think the FIP is clear. 

At a higher level, being able to use farcaster URLs in browsers, but also consume these URLs in farcaster clients I think it's very important.

For example, let's say I want you to be able to tel lemon3 to download the last dev call video from here: https://warpcast.com/fc1/0xaf4f7f13

Right now, there is no standard way for lemon3 to get the fid/hash of this cast. You have to use a wc-specific API, provided by wc. Tomorrow, there will be cb URLs, Zora URLs, etc. This FIP provides a simple, standardized way to translate a URL into the corresponding farcaster resource.

This too. But also the fact that we will have a number of apps translating URLs to farcaster URIs, and they will be ready to consume farcaster URIs. Also that devs will start thinking of farcaster resources as farcaster URIs, not wc URLs.

I understand the FIP and love the idea. The only part I’m not sure on is how it makes the introduction of farcaster:// easier down the line

Do you mean for example an app that renders URL previews could detect that a URL is linking to a cast and open the cast in your preferred client instead?