spent the last day fighting a gnarly issue (bug?) in how Next 16 Cache Components interact with atproto OAuth flow (cc @matthieu.bsky.team@bsky.brid.gy). might be a Next bug or not, anyway i filed github.com/vercel/next.... Cache Components causes fetch ...

to all who deem her unlikeable/cold/self-centered — what concrete things she could have said or done differently that would make you feel differently?

wait people think carol in pluribus is unlikeable??

in that sense i felt useful because i have enough technical taste to judge and nudge the ongoing process. there are many different ways it could’ve gone. having taste (i.e. experience) is useful now but maybe AI will be good at this too in the future

i need to figure out where to slap “use cache” well and as a bonus level maybe make it driven by redis or something. then i can maybe say i did full stack for reals

maybe it being outside the project dir makes it more obviously just for reference

*statusphere obviously

also feels so good to finally just have the data layer be drizzle calls instead of REST or GraphQL. that’s where i feel like the RSC paradigm shines, just read low latency whatever

shoutout @samuel.fm@bsky.brid.gy for his stratosphere railway template, i told claude to get inspired by it, and that helped with the ingestion part

the most important part is to clone good reference examples for it to get the style from, and to say which one is doing what better. then let it cook