Farcaster

the hardest part of building a farcaster client so far has been the volume of ecosystem changes

farcaster in 2023:
- decentralized twitter!
- thin layer of a protocol, feel free to build whatever experience you want
- we will decentralize everything soon

farcaster in 2024:
- frames
- cast actions
- power badge / priority mode
- channels
- composer actions
- actually, fuck power badge
- moxie / degen / 20x of random "hey what about you integrate our random sdk"
- streaks
- ok supercast has signups, cool, but its not on mobile so it cant be added to siwf
- ok we now have dms but only in one client so your customers will be angry that your client can't use these dms

not a rant just an observation

you need to adjust the perspective and the roadmap every month to survive here

really appreciate every single supercast subscriber who allows me to keep working on a farcaster client without any idea where this will go

important to keep in mind when thinking about adding to the protocol (or even exposing Warpcast APIs like Powerbadge)

decentralizing features before they are fully baked and proven creates drag on the ecosystem

KISS at the protocol, rapid experimentation at the product level

also we're lucky to have a builder like @woj.eth who can operate in the chaos

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

decentralizing features too early can create complexity, prioritizing stability and proven functionality