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
23 reactions
Lucas | POAP Studio
@gabo
>- 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 how is calling sdt html/js more complicated than the nice frame std ? if anything it make is much much more possible for (new) frame dev to exist all together
1 reply
0 recast
0 reaction
Samuel γ
@samuellhuber.eth
Building great webpages is harder then chaining post requests
1 reply
0 recast
0 reaction
Lucas | POAP Studio
@gabo
my comment was on existing frames/appframe, not **great** frames/appframe anything that shall be great has less throughput indeed π€£ for the sake of expanding i can imagine the https://replit.com/ workspace being a super easy appframe creation mechanism. today the niche is probably unmanageable byt current devs toolsets
1 reply
0 recast
0 reaction
Samuel γ
@samuellhuber.eth
current frames replit can already also do cc @zd who can comment on the experience
1 reply
0 recast
0 reaction
