i finally fixed caching! (i think) did -> handle, handle -> did, and did -> avatar lookups should all be getting cached in redis now which should considerably speed up navigations and stop 1s+ load times on some pages cause was fun: [github.com/vercel/next....]( ) [Docs: [Cache Components] "use ...]( )
i'm highly enjoying using [railway.app]( ) i think instead of starting with serverless, it would be good for many developers to start with Railway and then try serverless. i feel a lot more comfortable understanding the tradeoffs now [Railway]( )
ah too bad "use cache" still includes Build ID as one of the keys which defeats the purpose for me (i want the cache to survive deploys). i take it there's no way to work around (if i commit to stability myself) other than patching...
cool news, [sidetrail.app]( ) is now open source on @npub19y6x...yh78! the stack: - atproto (jetstream + new lex client) - next 16 + cacheComponents (yes, a recent version) - postgres + drizzle, redis - vitest [danabra.mov/sidetrail]( )
not convinced about doing anything complicated but this after every deploy gives me the incentive to finally try adding redis https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreiel2dgprbwdg2is2mvlkp5pibu4jauzgi2sb37aeaw3fqthe4cyca
ehh idk how i feel about liquid glass (just upgraded). i don’t hate it, but is there any particular app that really show it off? maybe i expected it to be more disruptive somehow
are there known issues with self-hosted Next.js behind Cloudflare breaking due to Cloudflare caching RSC responses?
people reporting being unable to tap buttons on ios, can anyone reliably reproduce this? i'll update my phone to ios 26 i guess but i haven't been able to repro so far RE:
cool writeup RE:
it says "on both clients and servers" right there RE: