Dan Romero on Warpcast

Content pfp

0 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

ok farcaster, let me introduce https://thefarcasterexperiment.com/ to you all basically, @dwr.eth claims that there were no breaking changes and only my stuff is broken or that neynar (cc @rish) had something broken well, let's test what @dwr.eth is saying. i launched a farcaster hub from ground up, then connected to it with official node js farcaster lib, then made @healthbot use this hub no third-party software. no me touching the backend, nodejs dependency or the hub let's see for how long this can last, i give it 2-3 months before there is a breaking change that makes me touch the code to make a thing as simple as publishing a cast every hour going again, all native farcaster hub stack, no extra dependencies, just something that "still works since the time it went permissionless" or whatever what are your bets? when will it break? this is a true stress-test of dev trust being broken or upheld

3 replies

0 recast

26 reactions

Dan Romero pfp

We are moving to a new version of the protocol in January called snapchain. So it will likely break then. We're not a mature, at-scale protocol. Still actively being built. I understand that you're busy with your own startup that you don't have time to follow along with all the changes. But the vast majority of active developers on the protocol, when surveyed, voted for moving faster and focusing on user growth vs. moving slower and making sure everything is stable.

2 replies

0 recast

2 reactions

borodutch pfp

@warpcastadmin.eth

coming back to the original topic, "how did farcaster break trust" this is how. this is my original feedback, there is no trust in whatever one builds surviving even 2-3 months without being touched and you're missing the larger set of devs that can spend some time (but not all their full-time work time) benefiting the ecosystem *most* of the things i remember using on farcaster (including 3rd party clients) from 2023 (or even early 2024) are not here today — and the most basic reason is the need to constantly support the software with never-ending breaking changes

2 replies

0 recast

1 reaction

Dan Romero pfp

There are 50+ developers who show up to the bi-weekly dev calls that are supportive of this direction and have enough time to keep up with the changes.

1 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

so, back to ignoring the feedback don't ask questions if you don't want candid answers

1 reply

0 recast

0 reaction

Dan Romero pfp

No, I'm specifically rejecting your claim that you represent the majority of developers on the network. People want us to iterate and improve the protocol. I'm not saying your feedback is not valid (I don't have time to keep up with changes), but you're very much in the minority of what developers are asking us for. Additionally, you never addressed the specific breaking change (on Neynar).

2 replies

0 recast

1 reaction

rish pfp

There have been no breaking changes on the API to post casts on our end. There has been a change to our notifications API which I think boro was using to listen to mentions of the bot. The new v2 API was launched in ~Feb/Mar 2024 and the v1 was finally deprecated in Oct 2024 so the transition time was more than 7 months and backwards compatibility was available throughout those 7 months. https://warpcast.com/rish/0x4446c267

1 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

> you represent the majority of developers on the network i never claimed this, you're strawmanning here i also absolutely do not say "don't iterate fast" what i'm saying is simply this: lack of backwards compatibility breaks trust as a response to you asking what exactly farcaster broke trust with this is my personal experience with the protocol

0 reply

0 recast

0 reaction