Listen, everyone is a critic and a Monday morning quarterback but I feel like channels were such a big missed opportunity for Farcaster. For the protocol and the client. Under-invested and not explored nearly long enough to definitively say they wouldn’t grow DAU, imo.

Writer. Head of Product @ Stablecore. Working on simple web hosting https://orbiter.host \ https://polluterofminds.com

the single most invested feature both in terms of ours and duration that we've built though

what would you change from what they are today?

@farcaster dev / dad / books, cooks, ski, code ~ there are many things of which a wise man might wish to be ignorant

from:dwr.eth channels

(need the dot eth) 

summary:
- new users find them confusing and they don't drive new growth
- half of users want them open and the other half want closed
- they are complex and need to be simplified before going on the protocol but there's no clear path to simplify since everyone has their perspective on how they should work

And to answer your question your question: I’d make them a client focus not an after thought. Meaning first class discovery feature and go back to suggesting casts get put in channels. 

I’d also make them a protocol primitive, which as I understand it, they are still not today. Or at least not fully permissionless and protocol based. Correct me if I’m wrong though

Not sure why this search doesn’t work but if it did I’d try to find the time Dan has said channels are not a priority