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](

sidetrail

trails worth walking

) 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](

danabra.mov/sidetrail

an app to share curated trails

)

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