Content
@
0 reply
0 recast
0 reaction
woj ツ
@woj.eth
just went over this, my thoughts: - as a user: strong support, this makes frames much more exciting to use - as a client dev: strong support, handling all the edge cases of frames right now is a mess. People only test on warpcast, warpcast does some things differently than neynar, devs don't care about testing on other clients. It's a mess like browsers were before chrome / webkit dominance - as a frame dev: mixed bag but positive. More extensibility, but harder to build simple experiences. I expect less frames being built, but of higher quality and from stronger teams additional points: 1. @v for "one shot frames" please let's add a "follow user" message. Optionally join / follow channel messages. These are common situations that people just link to warpcast to solve and it negatively impacts client diversity. 2. navigate to farcaster URL — does it mean we are getting a URI standard for farcaster resources?
3 replies
0 recast
22 reactions
Samuel ツ
@samuellhuber.eth
as a frame dev re "only test in warpcast" mostly we all test on local debuggers (think framesjs / frog) THOUGH tthere we have no local test neynar mock setup, so we can't test with that and then just ngrok to warpcast to have live signers Signers in local dev setups aren't persistet mostly or at least it's not known to most devs how/where to do that so we can test as close to live. Also not aware of another client besides warpcast having the debug tooling to check.
1 reply
1 recast
4 reactions
woj ツ
@woj.eth
yeah no blame on the devs, the state of things is natural — and it is a mess
1 reply
1 recast
0 reaction
Samuel ツ
@samuellhuber.eth
😘🤣https://warpcast.com/samuellhuber.eth/0x03bfbed6
0 reply
0 recast
0 reaction
