Zinger ↑ pfp
Zinger ↑
@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.
16 replies
31 recasts
72 reactions

Ryan J. Shaw pfp
Ryan J. Shaw
@rjs
A complete - server and client - set of reference implementations for an open source protocol is not entitlement, it's standard practice.
3 replies
1 recast
8 reactions

Zinger ↑ pfp
Zinger ↑
@zinger
Have you seen these from Merkle and Neynar? Or Opencast? Or Herocast? Or Nook? What else do you need? https://docs.farcaster.xyz/developers/ https://docs.neynar.com/docs/getting-started-with-neynar
1 reply
0 recast
1 reaction

Ryan J. Shaw pfp
Ryan J. Shaw
@rjs
The difference between a reference implementation sponsored by the protocol owner is that you can *trust* it is working to spec - in effect it is a part of the spec. Hobbyist clients are not the same thing. This is common practice, not entitlement. https://en.wikipedia.org/wiki/Reference_implementation
2 replies
0 recast
2 reactions

Samuel ツ pfp
Samuel ツ
@samuellhuber.eth
Does quikcast come close https://github.com/farcasterxyz/quikcast
1 reply
0 recast
2 reactions

Ryan J. Shaw pfp
Ryan J. Shaw
@rjs
Depends who you ask and what your intention is, I guess. I just take issue with calling people names like "entitled" - it's not productive. V wrote just yesterday it's not something they ruled out because it's something they have a fundamental issue with (i.e. that people are entitled for asking) - it's simply a matter of priority and maintenance effort (i.e. dealing with a bunch of people asking how to run Warpcast on a calculator, or demanding XYZ changes).
0 reply
0 recast
1 reaction