Dan Romero on Warpcast

Content pfp

0 reply

0 recast

2 reactions

Dan Romero pfp

Damn, Farcasters can ship! https://warpcast.com/alvesjtiago.eth/0x4f26cce2 https://warpcast.com/woj.eth/0x19fda812

2 replies

4 recasts

20 reactions

woj ツ pfp

if somebody wants to ship their first farcaster project to prod, give it a proper url and everything feel free to fork this https://github.com/wojtekwtf/fc-ama-formatter built with @neynar, can get some good views if you cache it nicely and give it a url like fcama.com/vitalik etc

1 reply

1 recast

2 reactions

borodutch pfp

@warpcastadmin.eth

if only it was as easy as forking to start working on it in the good old times it was now you have to doagic with signers, api keys, private keys, mobile sessions just to start developing for farcaster @dwr i've heard in your talk you want more devs, but revealed preference is the opposite it's extremely tedious

3 replies

0 recast

0 reaction

Dan Romero pfp

Revealed preferences: - Active developer count at an all time high - Most developers care about DAU and growth, willing to deal with some complexity assuming that exists

6 replies

0 recast

0 reaction

lucky pfp

0 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

ngl literally the same thing i've heard from the tg team when i was pointing out issues that can be easily solved ofc active devs are all-time high, the product grows and brings more people they aren't here because of the *unnecessary* complexity, but despite of it

1 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

what a dev needs to do now: 1. get an account seed 2. register with neymar and get its api key 3. register a signer (this is not the signer in usual lingo from #1) 4. get session key (make sure it isn't expired) 5. create client with session key 6. cast with session key and i'm sure i'm wrong somewhere (it's harder)

1 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

what a dev needed to do before: 1. get an account seed 2. use farcaster-js: create client 3. use farcaster-js: cast from client instance

0 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

i can see that this change was done because of hubs — and that's *totally ok* with everything taking into account decentralization benefits yes, having 1-2 steps more is ok if they are well-documented they aren't

0 reply

0 recast

0 reaction

borodutch pfp

@warpcastadmin.eth

like, think about it: would it hurt the ecosystem if users only had to do `new Client(wallet)` and then `client.publishCast(text)`? not in the slightest and this is how it always worked i'm even ok paying whatever $ to a third-party service that can abstract me away from unnecessary steps this is how bad it is

0 reply

0 recast

0 reaction