lemon3 is an open source program that uses IPFS and Farcaster to allow decentralized file hosting and sharing.

It's a mini Farcaster client and an IPFS node, and allows uploading and downloading files. Lots of rough edges, this is the mvp, but I'm very excited.

lemon3 is an open source program that uses IPFS and Farcaster to allow decentralized file hosting and sharing.

It's a mini Farcaster client and an IPFS node, and allows uploading and downloading files. Lots of rough edges, this is the mvp, but I'm very excited.

https://blog.vrypan.net/2025/03/23/lemon3-farcaster-ipfs-decentralized-file-sharing/

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

does it make sense for a user to publish casts with enclosures under an FIP-2 URL?

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

it seems easier to build on if there’s a specific entry point for “a feed of enclosures”, for example could plug in the root url and populate a blog

if it’s any random cast it’s hard to know what to do with them

Well... There was an FIP to standardize this, but never got through. "If someone builds something that makes sense, we may reconsider" :-)

Also, Warpcast does not support IPFS anyway (but this is not a limitation of the protocol), so the enclosure would be ignored anyway. To be fair, if someone shares a 3h movie in 8K, I wouldn't expect a mobile client to show it, anyway, regardless of protocol.

The timeline of @fc1 has a few embeds, and I'm fine with how they look.