AMA about Farcaster—why we made a decision, something that's confusing, strategy, product, etc.

Why shouldn’t devs be terrified that any useful/highly utilized cast composer action will just get coopted and released by the Merkle Team once utility is proven?

/cameron for content experiments. Helping Creators with /seemore. Yapping on /okbanger. Curating in /lounge. Dev + Veteran + HBS. 
seemore.tv/cameron 🫡

Obv I’m stoked to be here, but a more cynical person might observe that composer actions are a really clever way to offload exploratory dev work to external parties and survey what makes sense to seriously lean into

Sorta like the Amazon Basics of social tooling

because we opted to build composer actions in the first place as opposed to doing native polls?

Yea this is sorta my equilibrium opinion on all of it too

iirc there was some blog in the past about how to think about what kind of apps to develop for apple. the trick was _not_ to develop something that apple would obviously add later (e.g. a flashlight) because _everyone_ wants it, rather to focus on more niche use cases that only some minority % were interested in. this seems no different to me tbh

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

Good question to be asked and answered in public 🙏

Unlearning. Full time product manager. Part time builder/tinkerer on farcaster. Bots: @nftsoffc.

lol yea it's a bit dramatic framing, but given the language from Merkle around wanting to build an ecosystem sometimes being at odds with builder experience I wanted to directly ask the hardest version of the question

Don’t think devs should be terrified. They should expect it and operate that way imo.