Zinger ↑ is job hunting
@zinger
Open source this, open source that How about you open your code editor and build something yourself instead of demanding that a company give you all of the pieces you need? So sick of the entitlement from some devs on here, most apps wouldn’t even get retained usage if you could clone Warpcast anyway Enough.
17 replies
76 recasts
125 reactions
Stephan
@stephancill
Would agree with you if we were not talking about by far the most dominant client for a decentralized social protocol Companies (rightfully) don’t want to compete with warpcast so we are not seeing adoption of alternative clients, which totally undermines key features of decentralized social Warpcast being open source (even just as a reference) would help prevent a lot of expensive work from being duplicated and level up the average farcaster client standard
3 replies
1 recast
15 reactions
Tony D’Addeo
@deodad
> help prevent a lot of expensive work from being duplicated and level up the average farcaster client unfortunately neither of these would remotely pan out in practice, it wouldn't be a useful reference (too hacked together, too opinionated, too expensive to run, too much legacy cruft) an indie client is going to be better off building on Neynar APIs to start and adding differentiated features on the product side the right approach for open sourcing IMO is to identify core components that every client will need (i.e. syncing data from hubs (Shuttle), SIWF (AuthKit), potentially a wallet) and then invest into making unopinionated open source versions of those
1 reply
0 recast
4 reactions
Stephan
@stephancill
I understand your point of view and it’s why I agree that it probably won’t be worth the pain to clean up and open source now It could have panned out that way if it was intended to be an open source reference client from the beginning I would still argue that the lessons learnt from scaling to this point would be very helpful to the ecosystem, specifically regarding building performant algo feeds since that’s not exactly common knowledge and yet it’s a prerequisite for a competitive consumer social app. Perhaps a technical blog is better suited for that at this point
1 reply
0 recast
3 reactions
