writinghackathon

Free FIP-2!! My take on why FIP-2 is not only vastly under-explored, but also a primitive that could be core to Farcaster's growth

Published below on dylansteck.com as well as on my Paragraph blog, "Next in Tech"

https://dylansteck.com/blog/free-fip-2

paragraph.xyz/@dylsteck.eth/free-fip-2

building products in web3, hacking /farhack, yapping /dylan | dylansteck.com

It's permissionless. Make something interesting with it.

There’s a challenge in the way wc display the casts out of context. 

I’m using FIP-2 to create ephemeral (ish) channels yet in WC they show as disconnected casts & are displayed as ‘external content’ replies. 

Users HATE this. Some created seperate accounts to not have casts impact their main wc feed. 

I hate this as an app dev I need to care about what WC does. Permissionless yes. Free no.

Ethereum builder & people connector. @juicebox revnet.eth.sucks defifa.net d33m.com

a nice early iteration could be:
- showing the parent_url as a link embed where the "Content" cast would usually be
- (maybe) filtering by parent_url as part of fuzzy search

oh nvm the embed i was talking about already exists(nice), then maybe:
- render that embed as a frame if one exists(could be cool so that the dev has that surface to explain what's going on)
- show the replies to this parent_url below

there could be other nice things like changing the file icon and changing !12695 but I feel like those are lower pri

oh nvm the embed i was talking about already exists(nice), then maybe:
- render that embed as a frame if one exists(could be cool so that the dev has that surface to explain what's going on)
- show the replies to this parent_url below

there could be other nice things like changing the file icon and changing !12695 but I feel like those are lower pri

https://warpcast.com/~/conversations/0xe9d5ec21a71fcf2fe7a6b6f59f6962fba48b83ee

This frame idea might work for some app’s use of fip-2 but I doubt it will work for all. 

A beautiful property of FIP-2 is you don’t need to use replies to create context container. The parentUrl is the container. Imagine twitch like live chat w no replies. Each cast has FIP-2 parentUrl as its ‘channel’ rev chron.

Football

I don’t think your app should care about my app nor my app care about yours.

We should be able use the same identity & message types but different namespaces. If we want to display content that’s created in a different app go for it. Otherwise don’t show it. 

eg the only wc channel d33m.com displays is /football & only top level casts at that.

So - discovery is up to your app to decide what to do with my app’s exhaust. 

Wc notifies (superfollow) like crazy when people are casting in a d33m ‘room’. Very annoying to users of both apps.

Let's separate two things -- what's more important:

1. Displaying the parent URL vs. the generic component
2. Discovery of other casts