dylan

vercel

that casterscan live feed change made my edge requests & data transfer numbers go up like at least 5x on /vercel, gotta find some time one night this week to optimize the query a *little* bit more 🤦‍♂️

casterscan mini app updates:
- fixed the homepage so the stream doesn’t die, should always stay a firehose of recent casts
- uses openUrl and viewProfile to handle as many links as possible
- shows the name and FID of the app the cast was published from
- some smaller stuff that should make the UI and performance better

in the meantime if you feel like going into the code and seeing what i can optimize, here's the file that i'm pretty sure is causing those numbers to spike

the caveat is i know this route needs to be pinged a lot because it's fetching live data, i just feel like i gotta be able to optimize it a bit more

https://github.com/dylsteck/casterscan/blob/main/app/api/hub/stream/route.ts
https://warpcast.com/dylsteck.eth/0x2a5d2476

bringing mini apps to 1B users @base              dylansteck.com

^ also separately needs to be moved from hubs to snapchain quite soon

🔍 ensdata.net ✦ 🖼️ pugson.net/rfe ✦ 𝙽𝙾𝚆: design engineer @family ✦ 𝙿𝚁𝙴𝚅: @rainbow 🌈

ya I’m starting to realize this was a bad call/not the best work lol, thinking maybe I should just keep the hub calls client side and not make a route for it

anything in particular you’d recommend here?