Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction
Vladyslav Dalechyn
@dalechyn.eth
@horsefacts.eth, is there a particular reason for limiting `postURL` to 256 bytes? Folks that build frames using dynamic parameters are often putting the address as a parameter, and that already eats up 42 bytes, and sometimes they need two addresses in place. It forces to implement tricky serialization techniques.
2 replies
0 recast
3 reactions
horsefacts
@horsefacts.eth
Can you use state? 256 bytes is the limit in the frame message protobuf. We started with low limits for these with the thought that frame messages might be stored on hubs. These are possible to extend, but if state works, use that.
1 reply
0 recast
2 reactions
zho
@nakedfool
looks like there is no hacky solution to this :( we can't use state in the initial frame because it requires to be empty and two addresses in our dynamic path exceed the 256-byte limit for initialPath for multi-step frame. if there is any chance to extend this, it would be a huge help! :)
0 reply
0 recast
1 reaction
siobh_eth
@seanmc
+1+1 @horsefacts.eth we’ve tried every trick in the book and still unfortunately for some use cases the post url is too many bytes. Even just doubling this limit to 512 would solidly solve our issues here - is there any way we can help make this happen?
0 reply
0 recast
1 reaction
