Building (and sometimes breaking) farcaster
38231 Followers
@rish said it well - farcaster needs a different setup than we can provide. what we could provide: a protocol that's more decentralized, more distributed, and significantly less expensive to run and grow.
fyi - making upgrades to our elasticache cluster in the next few hours. could result in a short downtime for a few minutes during that window.
Clank clank on robinhood mainnet
seeing some issues on the farcaster network layer, actively looking into it right now
First - massive props to @dwr, @v, and the amazing team at Merkle for making Farcaster what it is today. @rish, the Neynar team, and I have been building infrastructure for Farcaster before hubs were a thing. Now we get to build the protocol itself. If you've ever shipped something on Neynar APIs, you know how much we care about developer experience. We'll strive to deliver the same energy into the protocol, client, and everything in between. Excited for the next chapter. Let's build 🪐
Amazing use of the reply ranking feature by @bountycaster on the conversation API that we launched last week.
In grad school, there were days I pulled all nighters playing DoTA or LoL with friends at USC’s GamePipe Lab. This week, I unintentionally stayed up extremely late trying to build software that’ll be used to power Farcaster. It was THAT fun! Building with software has been always fun for me. Coding agents have shortened the time span of the effort🔄reward cycle enough for it to feel as rewarding as a game today. Multiplayer software building mode is going to be even more interesting.