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), /weatherxm (work), @l--o--l (fun). Also https://paragraph.xyz/@purplesubmarine

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

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?

you'd need to write scripts to do this

any part of that that seems hard?