Content
@
0 reply
0 recast
0 reaction
David Furlong
@df
If you're a frames builder, what's your biggest painpoint with frames today?
12 replies
1 recast
14 reactions
Chinmay ๐ช๐ช๐น๏ธ๐ฟ
@chinmay.eth
1. Caches 2. Sessions
0 reply
0 recast
0 reaction
Lฮovido ๐ฉโ๏ธ๐๐ฑ
@leovido.eth
Having to set up the linter, Jest, etc. on every single new frame.
0 reply
0 recast
0 reaction
mass.framedl.eth
@masshesteria
Really a spec issue more than anything. Text input is awesome, but supporting 1-2 dropdowns instead would make design easier. Technically you can do anything with text input, but you might end up asking a lot from users to type the right thing
0 reply
0 recast
0 reaction
Lฮovido ๐ฉโ๏ธ๐๐ฑ
@leovido.eth
Error messages are not very readable/human friendly. It would be great if there was some sort of highlight in the code itself rather than having a call stack
0 reply
0 recast
0 reaction
Hoot ๐ฉ โ Devcon
@owl
serialized JSX passed to the image renderer route being too large and breaking ๐
0 reply
0 recast
0 reaction
tldr (tim reilly)
@tldr
cc @maxp.eth (It also seems to me that recently transaction frames have been getting deemphasized by the algo)
1 reply
0 recast
3 reactions
llamafacts
@llamafacts.eth
There is not an easy way to build a fullstack frames server (I.e having frames AND a landing page AND some other back end and serverless infra) across different services under the same domain. All tools are too focused on vercel and even then it's not straightforward.
1 reply
0 recast
1 reaction
Paul Gadi
@polats
a satisfying way to do animations!
0 reply
0 recast
1 reaction
Pau ๐ฉ โ๏ธโ๐ฅ
@p4u
Cache on warpcast side.
0 reply
0 recast
1 reaction
nezzar.eth
@nezzar.eth
Caches
0 reply
0 recast
0 reaction
Cameron Armstrong
@cameron
Frames are second class citizens in the warpcast feed so distribution is effectively capped to your own reach unless you lean into the shitty "recast and follow" meta
3 replies
0 recast
4 reactions
chun
@zkchun.eth
https://warpcast.com/colinrives/0x2e62f482
0 reply
0 recast
1 reaction
