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.

/new-york by day 🗽 /latenightcrew by night :) Fan of eating tacos and bringing people together, often at the same time 🌮 oh and /untzuntz 😈

A complete - server and client - set of reference implementations for an open source protocol is not entitlement, it's standard practice.

Have you seen these from Merkle and Neynar? Or Opencast? Or Herocast? Or Nook? What else do you need?

Husband, dad, dev • @dune.eth wizard • Ultimate Ⓜ️oxie Dashboard https://tinyurl.com/moxiedash • Ultimate Degen Tips FAQ https://tinyurl.com/degenfaq

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.

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

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

I've only done reads - and I believe you 😅

but ryan have you tried writing a cast to a hub following the official docs?

dude ive been in hell and it felt better than how those docs treated me

fortune cookie casts, memes, parenting, building frames, /framedl & /framedl-pro

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.

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.