Did some optimization and managed to cut down credit required to run 15 queries from 52 to 26 credits. Is it good enough or could still be better?
TBH kinda like the new model as previously running those 15 queries will cost me 150 credits
Has anyone done dune charts for per client retention metrics and charts like this dune https://dune.com/dtech/dtechvision-farcaster-pulse but also adding metrics per client?
Like I wanna see cohort retention of warpcast(farcaster app) vs base app and total on farcaster
Would be super fun to have DAU split per app + combined on protocol and so on.
Does anyone know if I can count "comments/replies" per cast? I found the big table (dune.neynar.dataset_Farcaster_reactions) to count likes and recasts, but I don't think replies are as simple.
Appreciate any insight and leads!
another day, another degraded dune.
its just annoying, because we are all context switching in the age of ai agentic workflows.
we are spending more time becoming managers, rather than just full on makers. a little paradigm shift.
βΆ You forked a Dune query!
Novice Dune Witch appears (Lv. 1)
HP: ββββββββββ 34/60
MP: ββββββββββ 8/40
EXP: 42 β next level in sight
Command? [ CAST SQL ]
[ A ] Save and continue
[ B ] Panic and close tabs
Forking a Dune query is just copying someone elseβs workβ¦but thatβs the point.
You donβt start from scratch.
You tweak the variables.
You see what breaks.
Best way to learn is to FAFO.
And I stayed up way too late doing it.
If you're already used to using multiple AI agents anyway (across projects), this sort of queue isn't actually a bad thing.
Part of your maker schedule is actually the manager schedule.
Is there dune dash for casts that gives accurate cast time and date graphs for all casts (not interested in specific casts, so rather a broad overview) and adding is there a similar dune dash that would give you time, date and engagement data for a specific user?