Content
@
0 reply
20 recasts
20 reactions
woj ツ
@woj.eth
the hardest part of building a farcaster client so far has been the volume of ecosystem changes farcaster in 2023: - decentralized twitter! - thin layer of a protocol, feel free to build whatever experience you want - we will decentralize everything soon farcaster in 2024: - frames - cast actions - power badge / priority mode - channels - composer actions - actually, fuck power badge - moxie / degen / 20x of random "hey what about you integrate our random sdk" - streaks - ok supercast has signups, cool, but its not on mobile so it cant be added to siwf - ok we now have dms but only in one client so your customers will be angry that your client can't use these dms not a rant just an observation you need to adjust the perspective and the roadmap every month to survive here really appreciate every single supercast subscriber who allows me to keep working on a farcaster client without any idea where this will go
33 replies
44 recasts
183 reactions
Andrei O.
@andrei0x309
For me this just looks like a protocol that was driven by the client, Farcaster should have been totally detached from Warpcast. My opinion is that the Farcaster ecosystem would have been much better if there wasn't any official client. I mean Warpcast could have existed, but built by a separate team, just as a client among other clients, and not driving the whole protocol. Instead of: "will just decentralizing" later why not build directly decentralized and there's no need for later? And frustration probably is larger because most web3 devs know what's decentralized and what's pseudo-decentralized. I mean is a pity to say it but at least at the moment lens fares better in terms of decentralization, and there were times when this was not the case.
0 reply
0 recast
2 reactions
