lemon3

lemon3 is an open source program that uses IPFS and Farcaster to allow decentralized file hosting and sharing.
The name is a tribute to iPodder Lemon, the original podcast aggregator, because it is intended to be a web3-friendly version of the original idea.
lemon3 uses cast.Embeds
to embed a special enclosure+ipfs://<CID>
link in casts. The link points to a json payload hosted on IPFS. The json payload is intended to make up for the fact that Farcaster Embeds
are plain links with no additional information that is required in this case (and could be very useful in other use cases too), and provides: file name, file type, file size and the IPFS CID of the file that was shared. This is the equivalent of the RSS <enclosure>
tag used in podcasting.
lemon3 is a mini Farcaster client, that connects to a hub: It will show casts containing enclosures from users you follow, and it allows you to share files by uploading them to IPFS and casting the corresponding enclosure. It also contains an embedded IPFS server, so you don’t have to run your own.
iPodder Lemon (2005) | lemon3 (2025)
---------------------- | --------------------------
RSS feed | Farcaster user casts
RSS enclosures | enclosure+ipfs:// Embeds
Files on web server | Files on IPFS
Web server required | No servers required
to host feed and files |
Status and next steps
Version 0.1.1 is the MVP: You can upload and share files, and you can find and download files shared by others.
But there’s a lot to be done to get to a version that “just works”: various bug fixes, UX streamlining, a decent user onboarding flow, and features such as keeping track of already downloaded files, support for standalone IPFS servers and a download manager. Maybe a web interface (similar to how Transmission works), too. Probably an RSS gateway that exposes these feeds as RSS for compatibility with existing podcast clients.
Even the core protocol design may need some updates, like replacing the JSON payload with IPLD.
But once everything is more stable, there are new opportunities that we did not have with RSS, like reactions and comments: For example, if you are producing a podcast, your listeners could reply, like and share your episodes, natively, within their social network.
I’m very excited with the possibilities!