my experience this weekend - did a few successful wild refactors (completely swapped data layer and removed a bunch of third party code, completely new end-to-end test suite) - reduced a very tricky bug to a minimal repro mostly autopilot but my feedback was absolutely crucial at every stage RE:
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 ...]( )
wait people think carol in pluribus is unlikeable??
claude code on a roll today (new opus genuinely seems good). i migrated my toy app from [@slices.network@bsky.brid.gy]( ) (it was a good first approximation) to handrolled oauth + jetstream ingestion + drizzle + atproto/lex client, and then squeezed out nice optimizations from direct db access. mostly hands-free
is there an example of using permission sets correctly (while docs are being written) or not really?
new opus looking good
wahhhh this is actually a good analogy RE:
log in with your internet handle [Internet Handle]( )
i think it’s ok to retire after this https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreic5n4jtxaydkc2qwtzvg4gxr3opstcfdvilkxlaxxsevvrk5534be
it would be nice if cacheComponents had a verbose mode where it logs every cache hit/miss together with the key. i know you can do something like that by writing your own handlers but i don't want to write any code, i just want a debugging tool