Farma is not there yet, but it's getting there.

Farma is not there yet, but it's getting there.

https://github.com/vrypan/farma

Building @warpcast and @farcaster / dad / like to read, cook, ski, code

Dad, geek, conversation liquidity provider. vrypan.net (home), @l--o--l (fun). devcoin:$lemon3

@deodad any ideas how I can stress-test it with hundreds/thousands of subscription updates?

you'd need to write scripts to do this

any part of that that seems hard?

Scripting is not my problem. The hard parts:

1. Notification status update JFS is validated, and the appKeys used are validated too. So, it needs to be valid appkeys, approved by the fids... Of course I could disable this check, but it's actually the only part of the flow that requires an external connection (to a hub), so it's also the least predictable (timeouts, errors).

2. Then, when sending the notifications, they must have real tokens...

Anyway, it's probably early, but I wander how could this be tested?

I don't think there's anything special or hard coded about Warpcast. You should be able to build your own mock FC client that can generate and handle notification tokens.

Not saying it'd be easy but most of the core utilities are present in

This does not solve #1. Notification subscriptions (frame add/remove, notifications enabled/disabled) signed by real signers, approved by the fids.

I don't think there's anything special or hard coded about Warpcast. You should be able to build your own mock FC client that can generate and handle notification tokens.

Not saying it'd be easy but most of the core utilities are present in https://github.com/farcasterxyz/frames/tree/main/packages/frame-node