What issue do you currently have indexing Farcaster data? 

e.g. using Replicator, Shuttle or APIs?

Developer 🤓 build, develop and operate Farcaster solutions @ dtech.vision also love tech, decentralization, fitness and oldschool rap 😎

Working on Airstack and Moxie | airstack.xyz | moxie.xyz | hihi! 


What do you wish shuttle had ? 

How’s your experience running it?

forked shuttle, made the message type processing concurrent 
hard to estimate how many concurrent workers to allow/configure + hardware requirements for a backfill

let alone how long it is too

also replicator schema hadn't been fully ported to shuttle schema
but ya I guess materialised tables are personal decisions

cookin' @tybb https://tybb.io, @consensys class '17

meh just ran it using bun, intermediary

trying to gauge ROI on backfilling the 1TB of data
will return to it later

shame there's no public process atm on just preloading shuttle Message schema with a downloadable snapshot
especially since the replicator > shuttle schema changed

cc @sidshekhar

Thought about just writing it in Rust? 

If you’re already making it concurrent and add parallelism why stay with nodejs?