vrypan |--o--|
@vrypan.eth
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/
22 replies
61 recasts
268 reactions
Tony D’Addeo
@deodad
does it make sense for a user to publish casts with enclosures under an FIP-2 URL?
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
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.
3 replies
0 recast
2 reactions
Tony D’Addeo
@deodad
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
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Oh, I see what you mean. Well, today, if you want to subscribe to my podcast, you subscribe to an RSS feed: `http..../feed.rss` using a podcast client. Not all entries have to include episodes (rss enclosures) but the ones that do, and they use a type of media compatible with my client (for example audio, not video or pdf), are downloaded. The equivalent is to use lemon3 to subscribe to @vrypan.
2 replies
0 recast
1 reaction
vrypan |--o--|
@vrypan.eth
It would be great if we introduced something like FIP-171 that would allow an enclosure to offer different representations of the same content type, for example an image preview and a video, which would allow more clients to render the enclosure.
0 reply
0 recast
0 reaction
Tony D’Addeo
@deodad
I still like the idea but in practice there's a fundamental tension between extensibility vs simplicity and compatibility. I think an elegant way to get adoption for these is to make them very application specific to start. I could image a paragraph style application that is built on FIP-2 + casts + enclosures (that only that app rendered, at least at first). there's all sorts of interesting things that could be done here and since it's all under a sort of app specific context it doesn't require other clients to support. makes it possible to use the root identity / broadcast system to build more specialized apps
2 replies
0 recast
2 reactions
