ipfs

Farcaster

Cohost /gmfarcaster livestream Farcaster news and culture show🎙️💬 Founder Tenger Ways, bringing joy into work with DevOps practices 🤗 mom x 3 💗

1) IPFS can be slow and unreliable
2) The network is less self sufficient because casts now depend on IPFS
3) Embeds rot over time if data is not pinned or preserved
4) Clients need to build custom UI for every possible extended cast type
5) Competing standards for different data types may fight each other

Love you horsefacts, but this is one of the most tired arguments against IPFS. If I run an HTTP server on my computer and expose the port to the world, anyone making requests to it would say it's slow and unreliable. That's why people don't do that when they need speed and reliability.

Writer. Building @pinatacloud. Working on simple static site hosting https://orbiter.host \ https://polluterofminds.com

Also... Farcaster Hubs themselves run on libp2p which is the same "slow" protocol built by the team behind IPFS

Building /indexing; love your data again. Probably also running 🏃‍♀️

libp2p is not the slow part. IPFS is not "slow" because it uses libp2p, but because it fetches content from remote peers in a DHT. A Farcaster peer has all or most content already and uses libp2p gossip to catch up, not to lazily fetch missing content.