tomato
@tomatoxyz
yes - but I guess it's a protocol/client question for Farcaster as a whole (I don't know if you work for Farcaster). A good example is the incongruency with channels and @cura - I right now want to post in /daos but there's no application process mentioned, but @cura has a button for "request to join"... what should I do? As an end user this kind of confusion is maddening and it feels like the responsibility for just this one thing is a game of hot potato between the protocol/flagship client (warpcast) and mini-app developers. IMHO the protocol should be taking ownership of basics. This kind of stuff may feel like nitpicking but Farcaster isn't new, doesn't have scarce funding and still having this kind of disparity for what is basic, inherent product functionality is what ends up in churning new/interesting users. End users don't want to delve into stuff this deep, nor try to figure out the game of hot potato - they have an attention span of about 0.32s before they go screw around on another platform.
1 reply
0 recast
2 reactions
Trigs
@trigs
I hear ya. I don't work for Merkle. I work for Farcaster in the sense of it being an open protocol so I'm putting together user requirements for theoretical clients to fit specific use cases with the hope that it'll help guide promising new devs towards building things that give us alternatives to Warpcast to experience Farcaster. Nothing against Warpcast. It's just Farcaster is pointless if we don't build a viable ecosystem outside of it. Warpcast will be great when we also have everything else we need. Warpcast will be like the fun version of social media we can escape to when we feel like it.
0 reply
0 recast
1 reaction
