Content pfp
Content
@
0 reply
20 recasts
20 reactions

ted (not lasso) pfp
ted (not lasso)
@ted
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
41 replies
12 recasts
169 reactions

nis.eth pfp
nis.eth
@literature
Hard to build a channel-focused client when channels aren't part of the protocol or there's no APIs!
4 replies
0 recast
26 reactions

ted (not lasso) pfp
ted (not lasso)
@ted
would you like that to change?
2 replies
0 recast
4 reactions

kbc pfp
kbc
@kbc
Yes. I’m blocking instead of muting because of the API. If I mute I’m customising my warpcast experience. If I block, my choices can be adapted by other apps
0 reply
0 recast
0 reaction