nyc-crypto-cabal-kid pfp
nyc-crypto-cabal-kid
@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
76 recasts
78 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
12 reactions

dusan.framedl.eth pfp
dusan.framedl.eth
@ds8
not taking sides in this debate, just came here to say reference implementations usually are just that. i'm afraid this argument wouldn't make merkle release warpcast code, just make them deliver a reference implementation.
1 reply
0 recast
2 reactions

Ryan J. Shaw pfp
Ryan J. Shaw
@rjs
Yes there's leeway in how one defines a reference implementation. Some companies will release the core of their product, some will release the entirety, and some will 'maliciously comply' and produce a 'samples' repository that never gets updated. The community would have to decide whether what's released is what they need, but surely one should start somewhere? For what it's worth, I'm on the "release the core" side, not the "release the entirety" side of things.
0 reply
0 recast
3 reactions