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](
Bluesky Social
Slices (@slices.network)
AT Protocol App network and SDKs coming soon. quickslice.slices.network https://tangled.org/slices.network/quickslice join the discord: https://...
 ) (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:
Bluesky Social
Jacquelyn Gill (@jacquelyngill.bsky.social)
This author has chosen to make their posts visible only to people who are signed in.
log in with your internet handle [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
fantastic explanation by [@storyhb.com@bsky.brid.gy](
Bluesky Social
Josh (@storyhb.com)
Working on React and Next.js at Vercel
 ), also maybe first example i remember of a feature being more immediately useful (in a sense) self-hosted compared to serverless/vercel [Next 16.0: "Use cache" is igno...](
GitHub
Next 16.0: "Use cache" is ignored in dynamic routes Β· Issue #85240 Β· vercel/next.js
Link to the code that reproduces this issue https://github.com/leo-cheron/next16-cache To Reproduce Create a Next.js 16 app with dynamic routes (e....
 )
does "use cache" automatically include cache() in-request deduplication? if yes, is there any downside to basically always writing "use cache: private" instead of manual cache() wrapping? considering "use cache: private" has no other server effect