since apparently the "build another client, not a priority rn, doesn't drive long term growth, etc" is the default response here

(despite the general sense that channels are a rushed, underexplored feature (potential new primitive) where the lack of prioritization and thoughtfulness has led to increased friction and a worse NUX)

is anyone building a channel-focused client? 

i'm incredibly excited about the promise of channels and promise to dedicate a portion of my time, energy, and resources to exploring this with you and supporting you

i am a force of nature, as some of you may know, especially when i'm motivated by both the mission and someone telling me i'm wrong

For anyone that’s investigated this, what’s the technical difficulty with a channel-focused client? Serious question.

/ted | exploring the onchain frontier | surfing @ venice, ca | eating @ gjusta / gjelina

Front toward enemy. @seyitaylor on twttr. 

Don’t think there’s much of a technical barrier, more of a product and GTM challenge

Not sure what @ted has in mind but I don’t think it makes sense to have an app that’s only focused on one (or a few) channels (too narrow) and I also don’t think people want to check channels individually (too much work) so you basically end up back with an algo feed similar to Warpcast et al

I do think they could do a better job of leaning into channels on WC but doubtful that there’s enough space to create an entirely different app